القائمة
Triage issues through the repository's Issue Tracker Contract Orbit state machine. Use when the user wants to create, inspect, classify, move, or prepare issues for implementation or review.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Turn a plan, spec, or PRD into one or more independently-grabbable issues, and publish them when repository publishing rules are clear.
Turn the current conversation context into a PRD and publish it to the project issue tracker when repository publishing rules are clear.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Review current worktree changes, fix blockers, record non-blocking technical debt, and create a git commit. Use when asked to review and commit, prepare a commit, finalize local changes, or run a pre-commit review.
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
| name | triage |
| description | Triage issues through the repository's Issue Tracker Contract Orbit state machine. Use when the user wants to create, inspect, classify, move, or prepare issues for implementation or review. |
Move issues on the project issue tracker through the repository-defined triage workflow.
Every comment or issue posted to the issue tracker during triage must start with this disclaimer:
> _This was generated by AI during triage._
Before acting, read the repository's issue tracker contract and the repository docs it points to. Treat those repository rules as the source of truth.
Use the issue type/category roles and state roles defined by the repository.
Every triaged issue should carry exactly the role cardinality required by the repository contract. If state roles conflict, issue facts are missing, or the tracker disagrees with the contract, handle it according to the repository's hard-stop rules.
Prefer AFK when the slice can be implemented, reviewed, and landed through objective repository gates. Use HITL only when safe advancement requires human interaction such as judgment calls, external access, design decisions, architecture decisions, or manual testing.
The maintainer can override at any time. Apply requested overrides according to repository rules.
The maintainer invokes this skill and describes what they want in natural language. Interpret the request and act. Examples:
Query the configured issue tracker and present three buckets, oldest first:
Show counts and a one-line summary per issue, then triage according to repository rules.
Gather context. Read the full issue: body, comments, configured metadata, role facts, reporter, dates, and relevant repository-defined sections. Parse prior triage records so you do not re-ask resolved questions. Explore the codebase using the project's domain glossary, respecting ADRs in the area. Read the repository's out-of-scope records and surface any prior rejection that resembles this issue.
Recommend. Decide the type/category, state, and delegation suitability recommendation using repository terminology, with reasoning and a brief codebase summary relevant to the issue. Continue toward the best valid outcome allowed by the repository rules.
Reproduce defects. For issues that the repository taxonomy treats as defects, attempt reproduction before choosing an outcome: read the reporter's steps, trace the relevant code, and run focused tests or commands. Report what happened: successful repro with code path, failed repro, or insufficient detail.
Handle missing information. If required information is missing, move the issue to the repository-defined missing-information state and record the specific questions in the repository-defined triage record. If the repository does not define a missing-information state, use a relevant available skill to ask the user for those facts; if no relevant skill is available, ask directly.
Apply the outcome. Use the repository's configured sections, templates, metadata, and state machine. Do not invent missing facts or skip required gates.
If the maintainer says to move an issue directly, trust them after checking the repository hard stops. Apply the exact role/metadata changes and write any required brief or record. Do not stop mid-flow except when the repository hard-stop rules require it.
When asking a reporter or owner for information, keep the repository-defined triage record structure and include:
Questions must be specific and actionable, not "please provide more info".
If prior triage records exist on the issue, read them, check whether the reporter or owner has answered any outstanding questions, and present an updated picture before continuing. Do not re-ask resolved questions.