fix

Applies ledger-recorded finding fixes to source files by fingerprint ID.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill fix-vickysrawat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/fix
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill fix-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running code reviews, security scans, or dynamic scans, findings pile up in ledgers with recommended fixes. Manually locating each finding, copying its fix into the right source file, and updating the ledger status is tedious and error-prone. This Skill automates that loop: give it a fingerprint ID and it locates the finding, applies the recorded fix, and moves the ledger entry from Open to Fixed. ## Core Features & Use Cases - Fingerprint-based lookup: Searches the code-review, security, and dynamic-scan ledgers in order for a FP-xxxxxxxx ID and identifies the source ledger automatically. - Confirmed, surgical edits: Displays the vulnerable code and proposed fix, waits for explicit yes/no/edit confirmation, then applies the change via str_replace to only the affected file. - Consistent ledger bookkeeping: Physically moves the finding block from ## Open Findings to ## Fixed Findings and updates summary counts, keeping checkin and PR gates accurate. - Guard rails: Refuses to fix dismissed, already-fixed, or manual-fix-required findings, and never marks a finding Fixed if the edit did not actually apply. - Use Case: After a security review flags a SQL injection issue as FP-a1b2c3d4, run the fix command with that ID, review the proposed parameterized-query change, confirm, and have both the source file and the security ledger updated in one step. ## Quick Start Ask the AI to apply the fix for fingerprint FP-a1b2c3d4 from the findings ledger to the source file.

Frequently Asked Questions about fix

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

FAQPage Schema
How do I apply a code review finding fix automatically?

Run the fix command with the finding's fingerprint ID, such as /fix FP-a1b2c3d4. The Skill searches the code-review, security, and dynamic-scan ledgers, shows the vulnerable code and proposed fix, and applies it after your explicit confirmation.

How do I find the fingerprint ID for a finding?

Fingerprint IDs follow the pattern FP- followed by eight hex characters. Search for them with grep "FP-" in CodeReviews/code-review-ledger.md, security/security-ledger.md, or dynamic-scan/dynamic-scan-ledger.md, or open the HTML report in a browser.

Can I modify the proposed fix before it is applied?

Yes. When the fix is displayed, answer "edit" instead of yes, describe the change you want, and the updated fix is shown again for confirmation before anything is written to the source file.

Why does the fix command refuse to apply a finding?

The Skill stops if the finding is marked manual-fix-required, has been dismissed, or is already marked Fixed. Dismissed findings must first be re-opened with /dismiss FP-xxxxxxxx --undo before a fix can be applied.

What happens if the vulnerable code is no longer in the file?

The Skill verifies the vulnerable snippet still exists before editing. If it is missing, it warns that the issue may already be fixed manually and asks whether to mark the ledger entry as Fixed anyway.

Does applying a fix update the findings ledger automatically?

Yes. After a successful edit, the finding block moves from the Open Findings section to Fixed Findings with the fix date and description, and the summary counts are decremented and incremented accordingly.