fix

Apply diagnosed code changes and verify repairs with tests.

1|Updated May 18, 2026

Search Tags:#testing #code review #debugging #fix #code changes #bug repair

Ready to run

npx skills add https://github.com/linenoize/topia --skill fix-linenoize

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/linenoize/topia/tree/main/skills/fix
Command: npx skills add https://github.com/linenoize/topia --skill fix-linenoize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a diagnosed bug or review finding into a concrete code change and verifies the result so broken behavior is actually repaired.

Core Features & Use Cases

Implementation fixes: Apply minimal edits to source code after a diagnosis or plan identifies the root issue.
Verification discipline: Run targeted tests, type checks, and linting after each change to confirm the fix holds.
Safe repair workflow: Handle bug fixes, review corrections, refactors, and integration issues without touching tests unless they are provably wrong.

Quick Start

Ask the fix skill to apply the diagnosed code change and verify it with the relevant tests.

Frequently Asked Questions about fix

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

FAQPage Schema

How do I apply a diagnosed bug fix and verify the code changes?▼

To apply a diagnosed bug fix, you make targeted file edits to repair the broken behavior and then run post-change test execution to verify the code changes hold.

What is the best way to handle code review findings and integration issues?▼

The best way to handle code review findings and integration issues is to apply minimal source code edits that correct the implementation, followed by running targeted tests and linting to verify the repair.

Can I use this workflow to fix broken behavior without modifying my test suite?▼

Yes, this repair workflow handles bug fixes and refactors without touching tests unless the existing tests are provably wrong, keeping the code correction minimal and focused.

How does post-change test execution work for software bug repair?▼

Post-change test execution for software bug repair involves running targeted tests, type checks, and linting immediately after applying code edits to confirm the fix actually resolves the broken behavior.

When do I need to run import and API validation during a code fix?▼

You need to run import and API validation during a code fix when the targeted file edits involve changing dependencies or interfaces, ensuring the repair remains correct and integration issues do not occur.