Menu
Turn issue-like requests into clear states, missing-info questions, or agent-ready briefs.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Maintain CHANGELOG.md as meaningful merges land. Use after merging a feature branch, before cutting a release, or when asked "what changed?".
Cut a GitHub release by updating changelog, validating release checks, creating a tag, and publishing with gh.
Ship current work through a GitHub pull request using git and gh.
Record durable architectural decisions in docs/adr with compact context and consequences.
Shared vocabulary for designing deep modules, interfaces, seams, and adapters.
Diagnose hard bugs by building a tight repro loop before changing code.
| name | triage |
| description | Turn issue-like requests into clear states, missing-info questions, or agent-ready briefs. |
| metadata | {"author":"mattpocock","version":"1.0.2"} |
Use this when reviewing a bug report, feature request, PR idea, or backlog item. Default to read-only analysis unless the user explicitly asks to write to GitHub or another tracker.
needs-triage: maintainer evaluation is still needed.needs-info: reporter must answer specific questions.ready-for-agent: enough context exists for an agent to implement.ready-for-human: needs human judgment, credentials, manual review, or product decision.wontfix: will not be actioned.Categories:
bugenhancementCONTEXT-MAP.md and relevant CONTEXT.md.ready-for-agent, write a concise agent brief.## Goal
## Context
## Acceptance Criteria
## Constraints
## Verification