auto-devBurn down a GitHub issue backlog hands-off with a FLEET of N parallel workers — each drives one issue through `implement-issue` → `merge-pr`, then takes the next, so N stay in flight. The orchestrator ABOVE those skills: ordering, NON-overlapping areas per worker, CI waits, verified merge state (wor
create-issueCreate a fully-seeded GitHub issue — not a bare `issue-create` call: template-compliant, carrying a brainstorm → spec → implementation-plan trail so a contributor can pick it up cold. ALWAYS reach for this whenever the user wants to open, file, add, raise, log, or track a NEW issue / feature request
create-prOpen a pull request for a finished feature branch — or a fix left on the default branch itself (debug-issue's hand-off), which this skill branches off first: push it through the guard, link its issue, gate the title, and open it ready when the full test passes (a draft when asked, or when the test i
debug-issueUse the moment a user reports something broken or behaving unexpectedly — a bug, failing or flaky test, crash, exception, stack trace, regression, build break, or integration failure — and use it BEFORE the first command you would run to investigate, not just before the fix. That first look is where
deliver-issueTake ONE idea or ONE planned issue all the way to a merged PR, hands-off — file or seed it with create-issue, build it with implement-issue, land it with merge-pr, each phase in a FRESH sub-agent context. Use when the user wants the whole chain run for a single item: "deliver issue 47 end to end", "
implement-issueTurn an existing GitHub issue into a finished pull request — the actual coding. Use when an issue carries a `🛠️ Implementation plan` checklist and the user wants it BUILT: worktree, draft PR, task-by-task commits ticked on the live issue, review, ready-flip. Triggers: "implement issue 47", "knock o
initMake a repository ready for the issue/PR lifecycle skills in one command — record its facts in the committed profile (`.claude/skills/repo-profile.md`: commit identity, build/test commands, labels, merge style, conflict hot-spots), converge its labels, issue forms, settings, topics and Pages source
merge-prLand an open GitHub pull request. Use whenever the user wants to MERGE, land, ship, or close out an open PR: waits for CI, applies corrections until mergeable (red checks, conflicts with the latest `main`, unresolved review), squash-merges, triages follow-ups, and tears down the branch and worktree.
migrate-legacyUse when upgrading, migrating, or modernizing a legacy application — outdated target framework, out-of-support runtime, obsolete APIs, old packages, or legacy idioms. Triggers on "upgrade this app", "migrate to .NET 10", "modernize this codebase", "this project targets an old framework", « mets à ni
review-followupsConsolide et met à jour les suivis ouverts des migrations (next_steps/deferred des migration/report.json + backlog du kit). Use whenever the user asks what remains open across migrated repos, wants a status of pending decisions, says a follow-up item is done, or decides to close/abandon one — trigge
review-sessionsRead the transcripts of PREVIOUS sessions and pull out the failures the kit itself caused — errors on kit scripts, gate denials, workers that died waiting, red kit suites — then cluster them by root cause, drop what main already fixed, and file what earns an issue through create-issue. Use when the
triage-backlogPrune and re-decide an EXISTING GitHub issue backlog: verifies which open issues are already fixed or superseded, clusters the rest by root cause, proposes ONE disposition each and executes only what the owner confirms. ALWAYS reach for this when the user wants to prune, triage, groom, re-decide, or