[Testing] Use when initializing, writing, reviewing or verifying performance/load/soak/capacity tests. --mode=verify --fix-loop (or --mode=green) diagnoses, fixes and remeasures with performance-review. Static bottleneck audits use performance-review.
The English summary is being prepared. Showing the original description.
[Code Intelligence] Use when building/syncing the code graph, querying callers/imports/tests, tracing flow, checking blast radius, linking APIs or exporting JSON/Mermaid. --mode={build|query|trace|blast-radius|connect-api|export}.
The English summary is being prepared. Showing the original description.
[Planning] Use ONLY when the user explicitly requests a product roadmap, roadmap update or milestone selection: outcome milestones, MVP scope, non-goals, risks, evidence gates.
The English summary is being prepared. Showing the original description.
[Code Quality] Review an exact pending commit when the commit skill selects lightweight review or the user requests it. --fix-loop repairs and re-reviews; no Git publication authority.
The English summary is being prepared. Showing the original description.
[Testing] Use when generating a demo video from E2E screenshots for current changes, a commit, pull request or named user journey, covering every relevant case.
The English summary is being prepared. Showing the original description.
[Documentation] Use when generating, smart-merging or refactoring the root AI context (CLAUDE.md, AGENTS.md) and its Claude/Codex projections. Config file only: project-config.
The English summary is being prepared. Showing the original description.
[Testing] Use when a workflow step or the user asks for runtime review of a UI, API, CLI or service against intended behavior. --rounds=0 reports only; --rounds=N bounds repairs.
The English summary is being prepared. Showing the original description.
[Utilities] Use when asking about or configuring the .claude/.codex/.agents/.opencode skills framework: command discovery/help, runtime modes, scoped settings, commit reviews, hooks, workflows or skill visibility. Explains options; changes only requested settings.
The English summary is being prepared. Showing the original description.
[Code Quality] Use when a workflow step or the user asks for a focused code-change review: staged, unstaged, branch diff or simple pull request. --fix-loop fixes and re-reviews. Complex pull request: workflow-review-changes; rationale: why-review.
The English summary is being prepared. Showing the original description.
[Documentation] Use when creating, revising, auditing or generating a presentation: narrative-led self-contained HTML deck with speaker notes and edit mode.
The English summary is being prepared. Showing the original description.
[Workflow] Research web sources and produce a cited, reviewed deliverable. --output={synthesis|business-eval|marketing|course}.
The English summary is being prepared. Showing the original description.
[Workflow] Reconcile canonical specs, test cases, integration tests and docs after code changes, bug fixes or PR reviews; verify changed behavior.
The English summary is being prepared. Showing the original description.
[Workflow] Take a new product from idea through architecture, an approved plan and scaffolding to a reviewed, tested foundation; hand the first slice to workflow-implement-spec.
The English summary is being prepared. Showing the original description.
[Workflow] Build or extend idempotent, environment-gated development/QC seeders with realistic data, change review and verified tests.
The English summary is being prepared. Showing the original description.
[Workflow] Use when reviewing a pull request or changes that are complex, risky or cross-module and need specialist reviewers: reviews, applies validated fixes, re-reviews. Defaults to --fix-loop; --review-only reports. Simple PR: changes-review.
The English summary is being prepared. Showing the original description.
[Category] Use when defining the standard skill description pattern.
The English summary is being prepared. Showing the original description.
[Workflow] Restructure existing code while preserving observable behavior, proven by baseline and final tests plus change review.
The English summary is being prepared. Showing the original description.
[Process] Use when the active workflow has finished its steps or the user asks to close it: checks outcome evidence and owned changes, then closes the workflow; recovery state stays until an explicit /clear.
The English summary is being prepared. Showing the original description.
[Workflow] Author canonical specs from existing code, update them after changes, or audit staleness; reconcile behavior and test evidence.
The English summary is being prepared. Showing the original description.
[Workflow] Create or revise the canonical spec for one capability in the configured format, with reviewed cases and reconciled test evidence.
The English summary is being prepared. Showing the original description.
[Workflow] Investigate and fix bugs, crashes or regressions at the root cause, with reviewed changes and regression tests that prove the fix.
The English summary is being prepared. Showing the original description.
[Testing] Use when a workflow step or the user asks for a local test run and read-only results summary.
The English summary is being prepared. Showing the original description.
[Code Quality] Use when reviewing UI code for accessibility, responsiveness, performance and UX best practices.
The English summary is being prepared. Showing the original description.
[Documentation] Use when a workflow step or the user asks for a refresh of every selected, evidence-applicable reference-doc scan target, or a --targets= subset, at once. One doc: scan; first-time setup: docs-manager --mode=init.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)