Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, "model-check this race", "prove this invariant", or when concurrency, retries, state machines, parsers, or unsafe code need more than tests.
The English summary is being prepared. Showing the original description.
Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, "is the model still true to the code", or after merges and refactors that touched verified code without rechecking it.
The English summary is being prepared. Showing the original description.
Sharpen a task before starting: the expert approach, what the user is really after, and the right level of specification. Use for /sharpen.
The English summary is being prepared. Showing the original description.
Restate in your own words what you think the user's goals are and what problem they're trying to solve. Use for /in-your-own-words.
The English summary is being prepared. Showing the original description.
Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch/PR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.
The English summary is being prepared. Showing the original description.
Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug/security and code-quality branch audits.
The English summary is being prepared. Showing the original description.
Catch the user up on what changed in this chat since their last message, in plain words and small visuals. List every item waiting on them with what they need to decide it from the reply alone. Use for /ketchup.
The English summary is being prepared. Showing the original description.
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
The English summary is being prepared. Showing the original description.
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
The English summary is being prepared. Showing the original description.
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
The English summary is being prepared. Showing the original description.
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
The English summary is being prepared. Showing the original description.
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
The English summary is being prepared. Showing the original description.
Summarize authored commits over a user-specified time period into a concise update
The English summary is being prepared. Showing the original description.
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
The English summary is being prepared. Showing the original description.
Cut AI tells from any writing.
The English summary is being prepared. Showing the original description.
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
The English summary is being prepared. Showing the original description.
Apply when integrating a new requirement into an existing design.
The English summary is being prepared. Showing the original description.
Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.
The English summary is being prepared. Showing the original description.
Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via plugin-dev:skill-development + unslop, optionally pulling fresh evidence from recent transcripts.
The English summary is being prepared. Showing the original description.
Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.
The English summary is being prepared. Showing the original description.
Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.
The English summary is being prepared. Showing the original description.
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.
The English summary is being prepared. Showing the original description.
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
The English summary is being prepared. Showing the original description.
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)