Agent skill

Fix

by alamenai in alamenai/terrae

Systematically fix issues found by /review or reported by the user

MITAuto-check passedDevelopment

Install Fix

skills CLI
$ npx skills add alamenai/terrae --skill fix -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install alamenai/terrae fix --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/alamenai/terrae.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/fix .claude/skills/fix && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
fix
GitHub stars
244
Token cost
~775 tokens
SKILL.md length
374 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Systematically fix issues found by /review or reported by the user

  • Works in 5 steps: Identify Issues → Plan the Fix Order → Apply Fixes → …
  • Development work in your project
  • SKILL.md covers Instructions and Common Fix Patterns
  • Calls git and npx

What it does

Fix is an agent skill from alamenai/terrae. Systematically fix issues found by /review or reported by the user

Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Mapbox and React. The repository describes itself as: Composable and animated components that replace imperative layers with simple props. The perfect companion for shadcn/ui. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/fix”

Requirements

  • Node.js
  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Edit, Write, Bash(git diff*), Bash(npx tsc *)

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify Issues
  2. Plan the Fix Order
  3. Apply Fixes
  4. Verify
  5. Review Changes

What it can do on your machine

Read from SKILL.md and the folder at commit ea9a480. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Edit
    • Write
    • Bash(git diff*)
    • Bash(npx tsc *)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fix loads about 775 tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 374 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~18
When it runs · the whole SKILL.md, loaded when a task matches
~775

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from alamenai/terrae at commit ea9a480, republished under its MIT licence (© alamenai). 374 words, ~775 tokens.

Download SKILL.mdSave it as .claude/skills/fix/SKILL.md (or your agent's skills folder).
name
fix
description
Systematically fix issues found by /review or reported by the user
allowed-tools
Read, Grep, Glob, Edit, Write, Bash(git diff*), Bash(npx tsc *)

Fix Skill

Systematically fix code issues found by /review or reported by the user.

Instructions

Step 1: Identify Issues

If coming from a /review, gather the issues from the review output. Otherwise, ask the user what needs fixing.

Categorize each issue by severity:

  • Critical — Compilation errors, missing imports, runtime crashes
  • High — Memory leaks, missing cleanup, security concerns, DRY violations
  • Medium — Convention violations, inconsistencies, naming issues
  • Low — Style preferences, minor optimizations
Step 2: Plan the Fix Order

Fix issues in severity order (critical first). Group related fixes together when they touch the same file to minimize changes.

Present the plan to the user before starting:

## Fix Plan

### Critical (fix first)
1. [Issue] — [File:line] — [What to do]

### High
2. [Issue] — [File:line] — [What to do]

### Medium
3. [Issue] — [File:line] — [What to do]
Step 3: Apply Fixes

For each fix:

  1. Read the file to understand the current code
  2. Apply the minimal change needed to fix the issue
  3. Verify the fix doesn't break anything nearby
  4. Move to the next issue

Follow these principles:

  • Minimal changes — Fix only what's broken, don't refactor surrounding code
  • One concern at a time — Don't mix fixes for different issues in the same edit
  • Preserve intent — Keep the original behavior while fixing the problem
  • Follow project conventions — Apply fixes using the patterns from .claude/rules/
Step 4: Verify

After all fixes:

  1. Run npx tsc --noEmit to check for type errors
  2. Show the user a summary of what was fixed
## Fix Summary

### Fixed
- [Issue] — [File] — [What was done]

### Skipped (needs discussion)
- [Issue] — [Reason]

### Remaining
- [Issue] — [Why it wasn't fixed]
Show full SKILL.md (156 more words)Show less
Step 5: Review Changes

Show the user the diff of all changes:

bash
git diff --stat

Ask if they want to proceed with committing or if adjustments are needed.

Common Fix Patterns

Missing Import

Add the import at the top of the file, grouped with similar imports.

Missing useEffect Cleanup

Add a return function that removes event listeners, cancels animation frames, clears timeouts, and removes map layers/sources/markers.

Untracked setTimeout/setInterval

Store the timer ID in a ref and clear it in the cleanup function.

Untracked requestAnimationFrame

Store the RAF ID and cancel it with cancelAnimationFrame in the cleanup function.

Replacing any with Proper Types

Identify what the value actually is and create a named type for it. Use unknown only as a last resort.

DRY Violations

Extract the duplicated code into a shared utility file. Update all files that used the duplicated code to import from the shared location.

Convention Violations

Reference .claude/rules/ for the correct pattern and apply it consistently.

© alamenai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/fix of alamenai/terrae.

Open the folder on GitHubat commit ea9a480

Compare with similar skills

Fix next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fix compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fix this skillalamenai/terrae244—~775Automated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Electron Multi-Process ArchitectureiOfficeAI/AionUi33k1 repos~1.8kAutomated safety check: PassApache-2.0
Nx Generatenomcopter/react-mosaic4.8k7 repos~1.9kAutomated safety check: PassCustom licence
@pierre/diffs Code Renderingpierrecomputer/pierre6.3k2 repos~803Automated safety check: PassApache-2.0
OpenTUI Terminal Interfacescline/cline70k—~1.9kAutomated safety check: PassApache-2.0

Similar skills

  • Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed
  • Tells the agent where new code belongs in an Electron multi-process project and which APIs each process may use, with rules for new bridges, services, agents and workers.

    33k GitHub starsUsed in 1 repo~1.8k tokens
    DevelopmentAuto-check passed
  • Nx Generate

    nomcopter/react-mosaic

    Generate code using nx generators. An agent skill from nomcopter/react-mosaic.

    4.8k GitHub starsUsed in 7 repos~1.9k tokens
    DevelopmentAuto-check passed
  • @pierre/diffs Code Rendering

    pierrecomputer/pierre

    Guides an agent through using @pierre/diffs to render syntax-highlighted files and diffs, and to build editing and review surfaces in React or plain JavaScript.

    6.3k GitHub starsUsed in 2 repos~803 tokens
    DevelopmentAuto-check passed
  • Helps build terminal user interfaces with OpenTUI using its core imperative API or its React and Solid reconcilers, with references for layout, keyboard, animation and testing.

    70k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Claude Code Skill

    codeaashu/claude-code

    Development conventions and architecture guide for the Claude Code CLI repository.

    3.4k GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed

More from alamenai/terrae

All 11 skills in this repo
  • Check

    alamenai/terrae

    Verify all outputs exist after creating a new component and fix any issues

    244 GitHub stars~1.1k tokensUpdated 6 mo ago
    Auto-check passed
  • Docs

    alamenai/terrae

    Generate or update documentation for Terrae components. An agent skill from alamenai/terrae.

    244 GitHub stars~576 tokensUpdated 6 mo ago
    Auto-check passed
  • New

    alamenai/terrae

    End-to-end workflow for building a new Terrae component from scratch

    244 GitHub stars~2.4k tokensUpdated 6 mo ago
    Auto-check passed
  • Perf

    alamenai/terrae

    Audit component performance and identify optimization opportunities with actionable fixes

    244 GitHub stars~678 tokensUpdated 6 mo ago
    Auto-check passed
  • PR

    alamenai/terrae

    Commit, push, and open a pull request on GitHub. An agent skill from alamenai/terrae.

    244 GitHub stars~767 tokensUpdated 6 mo ago
    Auto-check: notes
  • Commit

    alamenai/terrae

    Create standardized git commits following Terrae's conventions

    244 GitHub stars~568 tokensUpdated 6 mo ago
    Auto-check: notes

Works with

Categories

Questions about Fix

What does Fix do?

Systematically fix issues found by /review or reported by the user. Fix is an agent skill from alamenai/terrae.

When should I use Fix?

Fix fits situations like: development work in your project.

How do I install Fix in Claude Code?

Run `npx skills add alamenai/terrae --skill fix -a claude-code`. Or copy the skill folder (.claude/skills/fix in alamenai/terrae) into .claude/skills/fix in your project. Claude Code loads it when a task matches its description.

How do I install Fix in Codex?

Run `npx skills add alamenai/terrae --skill fix -a codex`. Or copy the skill folder (.claude/skills/fix in alamenai/terrae) into .agents/skills/fix in your project. Codex loads it when a task matches its description.

Can I use Fix in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alamenai/terrae --skill fix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix, .gemini/skills/fix, .github/skills/fix and .opencode/skills/fix in your project.

What does Fix need to run?

Going by SKILL.md and its folder, Fix needs the command-line tools its instructions call (git and npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Grep, Glob, Edit, Write, Bash(git diff*), Bash(npx tsc *).

Does Fix access the network?

SKILL.md contains no URLs. Its commands use git and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Fix safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Fix use?

Fix is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fix use?

About 775 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Fix?

Skills that share tags, products or a category with Fix: Vercel Composition Patterns (supabase/supabase, 111k stars), Electron Multi-Process Architecture (iOfficeAI/AionUi, 33k stars), Nx Generate (nomcopter/react-mosaic, 4.8k stars) and @pierre/diffs Code Rendering (pierrecomputer/pierre, 6.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix?

alamenai (a GitHub user) maintains it in alamenai/terrae, which has 244 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on April 6, 2026.

Source: alamenai/terrae on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.