Audit a codebase for unnecessary complexity, including dead code, duplicated state, redundant interfaces, and obsolete compatibility paths. Receive evidence-backed simplification candidates, or authorize changes that remove justified targets and validate the behavior that must remain.
Evaluate improvements to Archify diagrams using actual outputs and agent work records. Compare accuracy, readability, and total delivery time to investigate layout, connection routing, diagnostics, and authoring guidance, then document what the evidence supports.
Evaluate slow, unreliable, duplicated, or brittle tests by the behavior they protect and their maintenance cost. Use it to choose focused checks, justify additions or removals, and distinguish product bugs from outdated expectations or environment failures.
Review Archify issues, pull requests, and code by weighing user value, implementation and maintenance costs, and wider impact. Use evidence to decide whether work is worthwhile, compare alternatives, and identify questions that still affect the decision.
Turn plain-language descriptions, Mermaid diagrams, or repository evidence into interactive standalone HTML diagrams. Create system maps, workflows, timelines, database relationships, and everyday process diagrams, with automated validation, light and dark themes, and image, SVG, or WebM export.
Simplification audit or authorized codebase simplification whose stated objective is to remove accidental complexity. Use for evidence-backed deletion or consolidation of dead code, duplicate state, redundant APIs or layers, ownerless abstractions, obsolete compatibility or design records, and over-engineering in any language; also use for 代码简化 or 熵回收. Do not use for general code review, onboarding, style-only refactoring, or performance tuning.
The English summary is being prepared. Showing the original description.
Implement the result of /to-spec and /to-tickets in code.
The English summary is being prepared. Showing the original description.
Use when writing a PR body.
The English summary is being prepared. Showing the original description.
Conduct a retrospective on a coding session.
The English summary is being prepared. Showing the original description.
Convene a roundtable of sub-agents that debate a decision or proposal from opposing perspectives — parallel independent statements, anonymous cross-review, then a chaired verdict reporting consensus and dissent.
The English summary is being prepared. Showing the original description.
Wire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files. User-invoked.
The English summary is being prepared. Showing the original description.
Grill me about specs for the workflows I want to build, within this workspace.
The English summary is being prepared. Showing the original description.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
The English summary is being prepared. Showing the original description.
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
The English summary is being prepared. Showing the original description.
Implement a piece of work based on a spec or set of tickets.
The English summary is being prepared. Showing the original description.
Writing, exploit: shape raw material into an article, paragraph by paragraph.
The English summary is being prepared. Showing the original description.
Scan a codebase for deepening opportunities, present them as a report — HTML on request — then grill through whichever one you pick.
The English summary is being prepared. Showing the original description.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
The English summary is being prepared. Showing the original description.
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
The English summary is being prepared. Showing the original description.
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
The English summary is being prepared. Showing the original description.
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
The English summary is being prepared. Showing the original description.
Ask which skill or flow fits your situation. A router over the skills in this repo.
The English summary is being prepared. Showing the original description.
Stop. That last message did not land: re-pitch it.
The English summary is being prepared. Showing the original description.
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)