Skip to content

docs: sync example-skill.md copies with current narrow-react-prop-types skill #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ruttybob wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: sync example-skill.md copies with current narrow-react-prop-types skill #7

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 12 additions & 3 deletions ...ted-agentic-loop/skills/build-iterated-agentic-loop/references/example-skill.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ The goal is to make component types describe the real live-code-path contract, t

## Workflow

For an example recurring GitHub Actions workflow that runs this skill through CodeLayer, see `references/agent-narrow-component-props.yml`. Its example agent memory file is `references/narrow-component-props-memory.md`.
For an example recurring GitHub Actions workflow that runs this skill through CodeLayer, see `references/agent-narrow-component-props.yml`. Its example agent memory file is `references/narrow-component-props-memory.md`. For CI agent response formatting, see `references/response-template.md`.

### 1. Identify the suspect component

Expand Down Expand Up @@ -146,8 +146,17 @@ Use repository-specific validation commands when available. In this monorepo, pr
bun --bun run typecheck --filter <package>
```

### 11. Read the response template and format your final asnwer
Read the response template at `references/final-response-template.md` and format your answer accordingly.
### 11. Format the response

When running as a CI agent, format your final response according to `references/response-template.md`. This response becomes the PR body.

Include:
- Summary of how many components were narrowed
- Table of changes with rationale
- Live call sites that justify each narrowing
- Support code (stories/tests) that needed updating
- Validation results
- Risk assessment

## Review Checklist

Expand Down
15 changes: 12 additions & 3 deletions plugins/design-control-loop/skills/design-control-loop/references/example-skill.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ The goal is to make component types describe the real live-code-path contract, t

## Workflow

For an example recurring GitHub Actions workflow that runs this skill through CodeLayer, see `references/agent-narrow-component-props.yml`. Its example agent memory file is `references/narrow-component-props-memory.md`.
For an example recurring GitHub Actions workflow that runs this skill through CodeLayer, see `references/agent-narrow-component-props.yml`. Its example agent memory file is `references/narrow-component-props-memory.md`. For CI agent response formatting, see `references/response-template.md`.

### 1. Identify the suspect component

Expand Down Expand Up @@ -146,8 +146,17 @@ Use repository-specific validation commands when available. In this monorepo, pr
bun --bun run typecheck --filter <package>
```

### 11. Read the response template and format your final asnwer
Read the response template at `references/final-response-template.md` and format your answer accordingly.
### 11. Format the response

When running as a CI agent, format your final response according to `references/response-template.md`. This response becomes the PR body.

Include:
- Summary of how many components were narrowed
- Table of changes with rationale
- Live call sites that justify each narrowing
- Support code (stories/tests) that needed updating
- Validation results
- Risk assessment

## Review Checklist

Expand Down