القائمة
Use when a GitHub issue should be driven through clarification recovery, spec-build-test-QA-acceptance, and enforced human review gates with quality gates.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Autonomous code refactoring agent that rewrites messy functions, splits large files, removes duplication, improves naming, enforces structure, and preserves behavior.
Interact with Anytype's local REST API to manage spaces, objects, types, properties, tags, lists, and search.
Generate API integration test suites from Harnessy regression artifacts using a QA profile plus optional delivery-profile adapters.
Generate browser integration suites from Harnessy regression artifacts using a QA profile plus optional delivery-profile adapters for fixtures, routes, and helper imports.
End-to-end product development orchestrator with human-in-the-loop reviews.
Safe repo pull/push workflow that targets the repository integration branch, uses deterministic planning, and keeps PRs moving with a bounded autonomous resolution loop.
| name | issue-flow |
| description | Use when a GitHub issue should be driven through clarification recovery, spec-build-test-QA-acceptance, and enforced human review gates with quality gates. |
| disable-model-invocation | true |
| allowed-tools | Read, Write, ApplyPatch, Grep, Glob, Bash, Question |
| argument-hint | [continue|status|issue <number-or-url>] |
Drive one GitHub issue through the full Harnessy delivery lifecycle using the repository's existing skills, mandatory evaluation gates, explicit human review checkpoints, and strategy-aware intake when a standard docs/strategy/ folder exists. GitHub Project metadata is optional enrichment, not a required intake dependency.
Optional arguments: continue, status, or issue <number-or-url>
Template paths are resolved from ${AGENTS_SKILLS_ROOT}/issue-flow/.
${AGENTS_SKILLS_ROOT}/issue-flow/commands/issue-flow.md exactly.projects/<project-name>/worktrees/<issue_id>_<friendly_name> when viewed from the container, or ../worktrees/<issue_id>_<friendly_name> when invoked from projects/<project-name>/dev/, derived at runtime via ${AGENTS_SKILLS_ROOT}/issue-flow/scripts/issue_flow_git.py.${SPEC_ROOT}/<epic>/.issue-flow-state.json using portable git metadata only; never store machine-specific absolute worktree paths in tracked state.