From 24e3c2a9ea6ee0ea5ca9c39938455b4b31ec21d7 Mon Sep 17 00:00:00 2001 From: Sereja Date: Sat, 5 Sep 2026 16:48:20 +0300 Subject: [PATCH] sync example-skill.md copies with current narrow-react-prop-types skill Both build-iterated-agentic-loop and design-control-loop shipped a stale copy of narrow-react-prop-types as references/example-skill.md. The copy still pointed at references/final-response-template.md (a path that does not exist) and had a truncated step 11 with a typo ('asnwer'). Replace both copies with the current narrow-react-prop-types SKILL.md so the examples match the live skill: step 11 now references references/response-template.md and lists what the CI agent response (the PR body) must include. --- .../references/example-skill.md | 15 ++++++++++++--- .../references/example-skill.md | 15 ++++++++++++--- 2 files changed, 24 insertions(+), 6 deletions(-) diff --git a/plugins/build-iterated-agentic-loop/skills/build-iterated-agentic-loop/references/example-skill.md b/plugins/build-iterated-agentic-loop/skills/build-iterated-agentic-loop/references/example-skill.md index c1f197f..5ee3644 100644 --- a/plugins/build-iterated-agentic-loop/skills/build-iterated-agentic-loop/references/example-skill.md +++ b/plugins/build-iterated-agentic-loop/skills/build-iterated-agentic-loop/references/example-skill.md @@ -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 @@ -146,8 +146,17 @@ Use repository-specific validation commands when available. In this monorepo, pr bun --bun run typecheck --filter ``` -### 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 diff --git a/plugins/design-control-loop/skills/design-control-loop/references/example-skill.md b/plugins/design-control-loop/skills/design-control-loop/references/example-skill.md index c1f197f..5ee3644 100644 --- a/plugins/design-control-loop/skills/design-control-loop/references/example-skill.md +++ b/plugins/design-control-loop/skills/design-control-loop/references/example-skill.md @@ -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 @@ -146,8 +146,17 @@ Use repository-specific validation commands when available. In this monorepo, pr bun --bun run typecheck --filter ``` -### 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