feature-code-fix

Triage and apply code-review findings from feature folders via a subagent.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes and automates the workflow for triaging and applying code-review findings. It delegates execution to a dedicated subagent to ensure consistent, auditable changes across a feature's lifecycle.

Core Features & Use Cases

  • Delegates the entire execution phase to a single foreground subagent, which decides which findings to apply and records rationale in review-fixes.md.
  • Reads context from story.md, design.md, and review-fixes.md to align fixes with acceptance criteria and design decisions.
  • Updates Action Required checkboxes and keeps changes auditable, while respecting scope and safety constraints.

Quick Start

Invoke /feature-code-fix with the feature folder to begin triaging and applying findings.

Frequently Asked Questions about feature-code-fix

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

FAQPage Schema
How do I automate applying code review findings to a feature branch?

Automating code review fixes is handled by delegating execution to a dedicated subagent that reads review-fixes.md, decides which findings to apply, executes changes, and runs tests. It updates action-required boxes while preserving scope and maintaining an auditable history.

What is the best way to keep an auditable trail of code review fixes?

The best way to keep an auditable trail of code review fixes is by recording rationale for each applied finding in review-fixes.md. The skill updates action-required checkboxes and maintains auditable history while respecting scope and safety constraints.

How does a subagent workflow ensure code review fixes align with design decisions?

A subagent ensures fixes align with design decisions by reading context from story.md, design.md, and review-fixes.md before applying changes. This guarantees fixes match acceptance criteria and design decisions while updating action-required boxes.

Do I need specific markdown files to triage code review findings automatically?

Yes, you need story.md, design.md, and review-fixes.md files in a feature folder under ~/.claude/features/<name>/ to triage findings automatically. The skill reads these files to decide and apply fixes while running tests.

Can I run tests automatically after applying code review fixes?

Yes, you can run tests automatically after applying code review fixes. The skill executes changes delegated to a subagent and runs tests to verify the applied fixes before updating action-required boxes and preserving auditable history.

What are the limitations of automating code review fixes with a subagent?

Limitations of automating code review fixes include scope and safety constraints that the subagent must respect. It operates only on a feature folder under ~/.claude/features/<name>/ and will not apply findings outside the defined scope of story.md and design.md.