Apply review-identified fixes to project files under .claude/reviews.
npx skills add https://github.com/dixus/claudeframework --skill 3-fix
Please help me install this Agent Skill. Skill: 3_fix Source: https://github.com/dixus/claudeframework/tree/main/.claude/skills/3_fix Command: npx skills add https://github.com/dixus/claudeframework --skill 3-fix
This Skill automates applying fixes identified in a review to the project files, ensuring changes stay within the scope defined by the current spec and review phase.
Instruct the agent to apply the next review's fixes by referencing the .claude/reviews directory and the current spec constraints.
High-intent search queries and answers about installing and using this skill.
You can automate applying fixes by instructing the agent to read issues from the .claude/reviews directory and apply them directly to the explicitly mentioned files, ensuring changes are minimal and non-destructive. The Skill scopes changes to the reviewed files and verifies them against your spec.
Yes, automated review fixes stay aligned with your current spec and phase guidance by enforcing scope boundaries before making any edits. The Skill consults these constraints to prevent destructive changes, limiting modifications to the files explicitly listed in the review's Issues section.
To verify automated code fixes, the Skill runs the Typecheck, Lint, Tests, and Build commands listed in your CLAUDE.md file. It executes this verify workflow automatically after applying changes and reports any failures for further remediation.
The best way to scope code changes is to limit edits to the files explicitly mentioned in the Issues section of the review. This approach ensures modifications are minimal, non-destructive, and confined to the stated fixes without impacting unrelated project files.
Automated workflows might apply changes outside reviewed files if scope boundaries are not enforced against the spec and phase guidance. This Skill prevents that by consulting your current spec and restricting modifications to only the files explicitly listed in the review's Issues section.
Yes, you need a CLAUDE.md file containing your Typecheck, Lint, Tests, and Build commands to automate review fixes safely. The Skill integrates with this file to execute the verify workflow and report any test or build failures after applying the fixes.
ewe-studiosBootstrap Python projects with structured directories, environments, and pyproject tooling.
GolferGeekRun npm lint, format, test, and build before commits.
Jia-Hong-PengCreate a project constitution defining core principles, tech stack constraints, and MVP scope.
manatagoReview task implementations against specifications and boundary constraints with mechanical checks.
