fix-code
Properly fix code issues by following the quality assurance guidelines. Ensures comprehensive fixes across all related locations.
Best use case
fix-code is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Properly fix code issues by following the quality assurance guidelines. Ensures comprehensive fixes across all related locations.
Teams using fix-code should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/fix-code/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How fix-code Compares
| Feature / Agent | fix-code | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Properly fix code issues by following the quality assurance guidelines. Ensures comprehensive fixes across all related locations.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Code Fix Helper A skill for properly fixing code issues. Follows the core principles in `.claude/rules/fix-guidelines.instructions.md` to perform comprehensive and efficient fixes. ## Fix Flow Follow the common flow in `.claude/rules/fix-guidelines.instructions.md`. ## Code-Specific Fix Guidelines ### Code Deletion & Refactoring 1. Search all instances of the target pattern (verify with Grep) 2. Identify affected tests and documentation 3. Fix all related locations at once 4. Run build and tests ### Variable & Function Name Changes 1. Search all usage locations of the target (Grep + file type filter) 2. Check reference documentation as well 3. Change all at once 4. Verify build ### Error Handling & Logic Fixes 1. Search for the same pattern elsewhere 2. Check related call sites 3. Fix all at once 4. Run tests ## Self-Review (Code-Specific) After fixing, verify the following: - [ ] All affected locations have been fixed - [ ] The fix is correct - [ ] No build errors - [ ] All tests pass - [ ] Follows existing code style - [ ] Documentation needs updating as well? ## Practical Example ``` ❌ Bad example: Fix only 1 location - Fix only the reported location ✅ Good example: Search and fix all locations 1. Use Grep to search all instances of the same pattern 2. Fix the same pattern across all found files at once 3. Fix related tests as well 4. Run build and tests ```
Related Skills
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
framework
Expert on SpecWeave framework structure, rules, and spec-driven development conventions. Use when learning SpecWeave best practices, understanding increment lifecycle, or configuring hooks. Covers source-of-truth discipline, tasks.md/spec.md formats, living docs sync, and file organization patterns.
framework-learning
Learn and answer questions from any framework documentstion website quickly and accurately. Crawls a docs site from a seed URL, builds a lightweight URL index (titles/headings/snippets), BM25-ranks pages for a user's question, then fetehces and converts only the top-k pages to clean markdown for grounded answers with source links. Use when a user shares a docs URL and asks "how do I..", "where is..", "explain..", "OAuth/auth", "errors", "configuration" or "API usage"
framework-expert
Unified framework expertise bundle. Lazy-loads relevant framework patterns (React, Vue, Angular, Next.js, Node.js, Python, Laravel, Go, Flutter, Godot) based on detected tech stack.
framework-consciousness
Meta-orchestration skill for holistic TNF system understanding and coordinated capability use.
fp-ts-react
Practical patterns for using fp-ts with React - hooks, state, forms, data fetching. Use when building React apps with functional programming patterns. Works with React 18/19, Next.js 14/15.
fp-ts-pragmatic
A practical, jargon-free guide to fp-ts functional programming - the 80/20 approach that gets results without the academic overhead. Use when writing TypeScript with fp-ts library.
fp-ts-errors
Handle errors as values using fp-ts Either and TaskEither for cleaner, more predictable TypeScript code. Use when implementing error handling patterns with fp-ts.
fox-pilot
Firefox browser automation CLI for AI agents. Use when users ask to automate Firefox, navigate websites, fill forms, take screenshots, extract web data, or test web apps in Firefox. Trigger phrases include "in Firefox", "fox-pilot", "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", or any browser interaction request mentioning Firefox.
Fossil SCM Usage
This skill should be used when the user asks to "fossil commit", "fossil branch", "fossil merge", "fossil clone", "fossil sync", "fossil ticket", "fossil stash", "fossil timeline", mentions working with a Fossil repository, asks about Fossil vs Git differences, or needs help with Fossil SCM commands and workflows.
formula-decoder-skill
Decodes mathematical and physical formulas using a 5-stage process: Confusion, Intuition, Symbol Mapping, Limit Testing, and Dimension Ascension. Combines the styles of Feynman, Sanderson, Euclid, and Victor for deep understanding.
formsite-automation
Automate Formsite tasks via Rube MCP (Composio). Always search tools first for current schemas.