feature-code-review

Automate feature code review against story.md criteria and generate review-fixes.md.

1|Updated May 6, 2023
One-click install
npx skills add https://github.com/TobiasLaross/dotfiles --skill feature-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-code-review
Source: https://github.com/TobiasLaross/dotfiles/tree/main/agentic/skills/feature-code-review
Command: npx skills add https://github.com/TobiasLaross/dotfiles --skill feature-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow automates the review of implemented features by delegating verification to /review-code, using story.md acceptance criteria as the requirements source, and exporting structured findings to review-fixes.md for follow-up with /feature-code-fix.

Core Features & Use Cases

  • Delegated verification: Leverages /review-code to validate acceptance criteria against the feature implementation.
  • Context-aware review: Uses story.md (and design.md when present) plus repo context to ground findings.
  • Output-driven remediation: Generates review-fixes.md to guide remediation and track progress with /feature-code-fix.

Quick Start

Invoke the review by running /feature-code-review <feature-name> to start a feature code review.

Frequently Asked Questions about feature-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate feature code review using story.md acceptance criteria?

Automate feature code review by delegating verification to sub-agents that validate your story.md acceptance criteria against the implementation. This workflow grounds its analysis in feature context and generates a review-fixes.md file to guide remediation.

What is the best way to structure code review fixes for follow-up actions?

Structuring code review fixes involves exporting actionable findings to a review-fixes.md file. This output document tracks remediation progress and coordinates directly with downstream fixing workflows to ensure full traceability.

How does context-aware code review work when a design document is present?

Context-aware code review uses the story.md requirements and design.md specifications alongside repository context to ground the analysis. This ensures the automated verification accurately reflects the intended feature design.

Do I need a specific repository structure to run an automated feature code review?

You need a repository structure containing a story.md file for requirements and optionally a design.md file. The workflow requires access to this feature context to successfully verify implementation criteria and output findings.

Why should I use an automated workflow instead of manual feature code reviews?

An automated workflow coordinates with sub-agents to ensure full coverage and traceability across complex feature requirements. It accelerates the review process by systematically validating story.md criteria and producing actionable remediation recommendations.

Can I track feature remediation progress using the generated review output file?

You can track feature remediation progress using the generated review-fixes.md file. This structured output document logs verification findings and coordinates with fixing workflows to manage follow-up actions.