hayamiz-agentkit

Merge the reviewed worktree fixes (ticket/NNNN-<slug> branches carrying source + tests only, marked Review-state ready-to-apply in their main-tree ticket) into your current branch, then move each ticket open → resolved and commit it. Never auto-merges — this is the human gate. Use after /ticket-review approves fixes, or after /ticket-fix reports fixes that skipped review.

List all currently open tickets in the project's ticket directory. Read-only summary of file-based work items (distinct from GitHub Issues).

Implement fixes for tickets triaged as mechanically fixable. Trivial fixes edit in place; non-trivial fixes run in an isolated git worktree that carries source + tests only (the ticket stays in the main tree), checked by an independent reviewer (the Codex CLI when available, else a Sonnet evaluator subagent), and landed on your branch only via /ticket-apply. Review-gate progress is a Review-state marker in the ticket's Resolution, not a status. Claims each ticket with a lock so parallel runs don't collide. Does not merge to your branch.

Human review gate for worktree fixes awaiting review. Discovers fixes by their main-tree ticket's Review-state marker (their status stays open) plus live worktrees/locks, presents the full review material (summary, functional impact, diff, traceability, verification/reviewer provenance, change map, risk) — inline for small changes, as a Claude Artifact for large ones — then, on your OK, rewrites the marker to ready-to-apply. Human-only. Use after /ticket-fix reports fixes awaiting review, before /ticket-apply.

Initialize the project's ticket directory. Resolves (or declares) the ticket path in CLAUDE.md, creates the directory and its CLAUDE.md, and offers to migrate pre-existing ticket-like directories (e.g. doc/issues/).

Triage all open tickets in the project's ticket directory — classify by complexity, whether a mechanical fix is possible, and whether the fix needs a user decision.

Validate ticket files and inspect claim locks. Checks frontmatter schema, the status<->location invariant, unique numbers, and lock consistency (orphan/stale). Runs the bundled ticket-state.sh script. Use to check ticket health or before/after a batch of fixes.

Relentless one-question-at-a-time interview that stress-tests an open ticket's plan, sharpens fuzzy language, and crystallises decisions inline into the ticket's Implementation Notes section. Use when the user wants to harden a ticket before fixing it.

Create a new ticket in the project's ticket directory. Tickets are file-based, numbered work items tracked in the repository (distinct from GitHub Issues).

Audit and improve repository health — docs sync, best practices, skill extraction, and maintenance recommendations

Resync gardener support-file checklists (best-practices, security, etc.) against their upstream reference URLs, or add a new reference URL to a checklist. Parameterized by target file.