dev-skills

Explicit-only navigator for the dev-skills workflow. Use when the user names dev-auto or explicitly asks for workflow guidance across requirements, implementation, verification, and delivery. Recommends the next step from current evidence; does not execute the workflow. Generic implementation requests or an isolated "what next" do not trigger it. Supports [slug], --status, --next, and --recover.

Review a requested Git diff for bugs, regressions, integration gaps, and material risks before commit. Use for review requests and the review phase of requests such as 帮我 commit. A request for only a commit message belongs to dev-commit-writer. Review is read-only; a broader authorized commit workflow may continue after review.

Write a commit message from a requested Git diff when the user asks for message generation. Does not review, stage, or commit. Requests such as 帮我 commit require the commit workflow, including review when required; asking for a message does not require an explicit skip-review declaration.

Establish or update persistent product and visual design guidance in .design-context.md. Use for initial design setup, a deliberate design-direction reset, or explicit 设计上下文 requests. Discover existing users, components, tokens, assets, and constraints before asking about material gaps. Does not implement UI; ordinary UI work does not require repeating this setup.

Complete an implemented development branch through an authorized local commit/merge, push and PR, preservation, or discard. Inspect scope and applicable verification before delivery; respect an already selected action without repeating a menu. Does not replace implementation or review.

Investigate bugs, regressions, failing tests, or broken behavior by tracing evidence to the root cause, then implement and verify a scoped fix when requested. For explanation-only requests, diagnose without editing. Does not handle new feature design or commit-message-only requests.

Clarify feature requirements, pressure-test scope and domain terms, and produce a feature spec before implementation. Use for fuzzy requirements, PRD/spec requests, 需求对齐, 拷问需求, or 设计文档. Read existing evidence before asking focused questions. For concrete implementation planning use dev-plan; a generic "do not edit code" instruction alone does not trigger intake. Supports --quick, --deep, and --spec-only.

Implement a frontend from a UI screenshot or design image in an existing project or a runnable standalone page. Use for "UI图生成代码", "看图写页面", "根据设计图实现", "screenshot to code", or "image to code" requests. Preserve visual fidelity and working control semantics, then verify in a real renderer. Not for redesigns without a reference image.

Create a concrete implementation plan from a spec or clearly scoped request before coding. Use for implementation-planning requests such as 出个 plan, 技术实施方案, plan this, or consensus plan. Ground steps in the repository and scale tradeoff analysis and independent review to risk. Clarify material requirement gaps when needed; do not force an intake workflow for already clear scope. Supports --quick and --deliberate.

Compatibility alias for dev-grill-docs spec-only mode. Use for explicit dev-spec requests, old dev-spec workflows, or spec-only output without CONTEXT.md / ADR updates. Ordinary requirement alignment belongs to dev-grill-docs. Preserves the feature artifact and acceptance contract, including when installed standalone.

Implement scoped behavior changes using meaningful tests before code where practical. Use for features, behavior-preserving refactors, and direct fixes with a known cause; use dev-fix for bug investigation. Documentation, formatting, and asset-only edits do not need this coding workflow.

Verify implemented changes before claiming they are complete, fixed, passing, or ready for delivery. Match checks to requested behavior and risk, inspect current evidence, and report limits. Use for completion checks, not general factual answers or a replacement for code review.

Query Swagger/OpenAPI sources for modules, endpoints, request/response fields, reusable schemas and DTOs, or export Markdown/JSON API documentation. Use with Swagger UI, Knife4j, FastAPI docs, Redoc, OpenAPI JSON/YAML, and Swagger 2.0 URLs or local specifications, including endpoint integration lookups.