dev-kit-review_skill

Overview

This skill reviews completed tickets by verifying implementations against the User Story and all Acceptance Criteria. It focuses on evidence-based code inspection, tests, documentation, and project standards to produce a clear verdict. The outcome is an actionable decision: approve, request changes, or reject with concrete feedback.

How this skill works

Load a single completed ticket from .dev-kit/tickets/completed/, parse the frontmatter (Title, Category, User Story, Acceptance Criteria), and identify the scope. Use code analysis tools to inspect modified files and tests, verify each Acceptance Criterion against the implementation, check quality standards, and produce a verdict with actionable feedback and next steps.

When to use it

• A ticket has been moved to completed and needs verification before archiving or merging.
• Performing QA on an implemented feature to confirm it meets the User Story and ACs.
• Verifying bug fixes before they are merged into main branches.
• When preparing release notes and you must ensure changes are documented and tested.
• Enforcing project standards and preventing regressions during code review.

Best practices

• Review one ticket at a time and focus strictly on the listed User Story and ACs.
• Restate each Acceptance Criterion and attach direct evidence (file paths, function names, test results).
• Run or reference unit/integration tests and include test status in the verdict.
• Check documentation, error handling, and adherence to .dev-kit/docs/TECH.md coding conventions.
• Provide concise, actionable feedback: what to change, where, and why; include code-level hints when possible.

Example use cases

• Validate a new feature implementation matches the User Story and passes all Acceptance Criteria before archiving the ticket.
• Confirm a bug patch addresses all reported failure modes and has tests that reproduce the bug and guard against regression.
• Review enhancements to ensure backward compatibility and that documentation and changelogs were updated.
• Assess chore or infra changes to confirm build/lint/test pipelines still pass and configuration is correct.