القائمة
Worker skill for batching PR comments, bot findings, and CI failures; classify each item, fix real issues, reply with parser-recognized wording, and push one coherent update.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Implement one story into a story branch and open a PR into the epic feature branch using the repository's story workflow.
Run Go repository quality checks and decide which checks apply before story PR readiness.
Perform a local persona review before a story PR or final PR is marked ready for human approval.
Create or update focused unit, integration, or SAM sandbox e2e tests for implemented stories.
| name | address-bot-comments |
| description | Worker skill for batching PR comments, bot findings, and CI failures; classify each item, fix real issues, reply with parser-recognized wording, and push one coherent update. |
| triggers | ["review loop","bot comments","CI failure","pull request feedback"] |
This is a worker skill, not a reviewer skill. Use it when the orchestrator has batched PR review events for one PR/head SHA.
Do not launch a reviewer for each comment. Process the full batch in one worker run. If you push a fix, the orchestrator will request a single follow-up review after the worker is done.
Use gh to snapshot the PR before changing code:
gh pr view <pr> --json number,url,title,headRefName,headRefOid,baseRefName,isDraft,mergeStateStatus,reviewDecision
gh pr checks <pr> --json name,state,bucket,link,description
gh api "repos/{owner}/{repo}/issues/<pr>/comments" --paginate
gh api "repos/{owner}/{repo}/pulls/<pr>/comments" --paginate
Use GraphQL for unresolved review threads when available.
Classify every item before acting:
| Verdict | Meaning | Action |
|---|---|---|
| Fix | Real issue | Modify code, tests, docs, or traceability; run checks; push. |
| False Positive | Tool or bot is wrong | Reply with recognized wording and evidence. |
| Intentional | Behavior is by design | Cite ADR, story, or code evidence. |
| Out of Scope | Belongs to another story or PR | Page human if blocking or reviewer is strict. |
Use parser-recognized wording from config/worker-reply-patterns.json. The
orchestrator uses the same file to ignore worker replies, so do not invent new
prefixes without updating that config.
Before replying, open the config and choose the matching pattern. Include code, test, ADR, or story evidence after the required prefix.
When CI fails, diagnose immediately:
Escalate after three failed fix attempts for the same CI failure signature.
For each thread:
Before marking the PR ready, verify zero unresolved blocking threads remain.
Return a concise summary: