CheckPickerUpper

Audit GitHub issues against repository state or evidence-backed acceptance criteria, then reconcile confirmed issue changes through one complete Issue Plan.

File or reconcile one or more GitHub issues from Work Type templates through one complete Issue Plan, with clarifying questions, native parent and blocker routing, evidence-backed acceptance criteria, and agent attribution. Use when the user says 'file an issue', 'open a bug', 'log a feature', 'track this task', 'turn these findings into issues', or runs a /github-coordination:file-*-issue or /github-coordination:to-issues command.

Create or update a repo-local announcement through one complete Issue Plan, preserving bot attribution and optionally pinning the resulting issue. Use when the user says 'post an announcement', 'announce the release', 'update the pinned notice', or runs /github-coordination:create-announcement or /github-coordination:update-announcement.

Show open issue trees, blockers, linked pull requests, announcements, and issues waiting on evidence from GitHub's native coordination state

Turn a supplied report, audit, or backlog slice into one coordinated issue plan with native parent and blocker relationships

Audit GitHub issues against repository state or evidence-backed acceptance criteria, then reconcile confirmed issue changes through one complete Issue Plan.

File or reconcile one or more GitHub issues from Work Type templates through one complete Issue Plan, with clarifying questions, native parent and blocker routing, evidence-backed acceptance criteria, and agent attribution. Use when the user says 'file an issue', 'open a bug', 'log a feature', 'track this task', 'turn these findings into issues', or runs a /github-coordination:file-*-issue or /github-coordination:to-issues command.

Create or update a repo-local announcement through one complete Issue Plan, preserving bot attribution and optionally pinning the resulting issue. Use when the user says 'post an announcement', 'announce the release', 'update the pinned notice', or runs /github-coordination:create-announcement or /github-coordination:update-announcement.

Set up or edit .claude/ai-lab/perfect-typescripter/config.json to tune TypeScript enforcement rules. Use when the typescript guard blocks writes and the user wants to disable a rule, add exemptions, or configure the enforcer, or when the user says 'configure typescripter', 'disable boolean rule', 'add exemption', 'typescripter config'.

Set up ESLint integration for perfect-typescripter's four cross-file rules. Use when the user says 'set up linting', 'wire up eslint', 'how do I run the cross-file rules', 'set up perfect-typescripter for this project', 'install perfect-typescripter integration', or when a TS project (tsconfig.json or .ts files) has no eslint.config.* / .eslintrc.* in the project root.

Manual escape hatch to wire eslint-plugin-perfect-typescripter into the current project. The setup-eslint-integration skill normally does this proactively without typing the command.

Set up or edit .claude/ai-lab/perfect-typescripter/config.json to tune TypeScript enforcement rules. Use when the typescript guard blocks writes and the user wants to disable a rule, add exemptions, or configure the enforcer — or when the user says 'configure typescripter', 'disable boolean rule', 'add exemption', 'typescripter config'.

TypeScript enforcement rules. Auto-loads when Claude writes .ts or .tsx files so the rule context is in sight before the first line goes down. Contains the bans on null, undefined, optionals, booleans, any, unknown, enums, type assertions, and positional args; PreToolUse hooks enforce them and will block writes that violate them.

Set up ESLint integration for perfect-typescripter's four cross-file rules. Use when the user says 'set up linting', 'wire up eslint', 'how do I run the cross-file rules', 'set up perfect-typescripter for this project', 'install perfect-typescripter integration', or when a TS project (tsconfig.json or .ts files) has no eslint.config.* / .eslintrc.* in the project root.

TypeScript enforcement rules. Auto-loads when Claude writes .ts or .tsx files so the rule context is in sight before the first line goes down. Contains the bans on null, undefined, optionals, booleans, any, unknown, enums, type assertions, and positional args; PreToolUse hooks enforce them and will block writes that violate them.

Total annihilation: no finding survives unless it survives refutation. An unusually strict maintainability and structural-quality audit of a diff — review frame, intent/spec fit, repo standards, abstraction quality, cohesion, type/boundary cleanliness, duplication, control-flow tangles, and correct-by-construction opportunities. Use for a deep code-quality audit, a harsh pre-merge review, or to determine what structural change makes a class of bug impossible rather than merely caught. Stricter than a conventional review because every finding must survive an adversarial refutation pass, ship with a concrete before→after, and prove it preserves behavior. Severity theater is prohibited: only provable findings are reported.

User-invoked modifier for evidence-first read-only investigation. Use when the user appends /readonly to a question or another skill request: answer by checking the codebase and available read-only sources, do not implement, do not open issues, do not mutate local or remote state, and do not guess with 'likely' or 'probably' when evidence can be gathered.

Justify by correctness, never by convention. Use when a design, fix, API, macro, library surface, hook message, or naming decision is defended by 'it's what the codebase does', 'the established pattern', 'the canonical lane does it', 'more ergonomic', 'less churn', 'already wired', 'smallest fix', 'compatibility', 'legacy path', or 'out of scope to change'. Prevalence and transition size are not evidence. Re-derive from correctness, name the bug the alternative causes, and be confident in the correct call even when the codebase already happens to do it.

A high-judgment design interview that sharpens plans in useful batches and records settled domain language and ADRs as the conversation progresses.

Break a plan, spec, or PRD into independently-grabbable issues using tracer-bullet vertical slices, then wire the blocked-by/parent relationships into native GitHub sub-issues and dependencies so the tracker renders the real tree (not just prose). Use when converting a plan into issues, creating implementation tickets, or breaking work into slices.