agentleFS
Sign inStart free
vibe-cokitvibe-cokit/claude-code/skills/vk-fix-fast/SKILL.md

vk-fix-fast

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

⚡ Analyze and fix small issues [FAST]

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use debugger subagent to find the root cause of the issues and report back to main agent.

    line 19
  2. Distinctive:

    Start implementing the fix based the reports and solutions.

    line 21
  3. Very specific:

    Use tester agent to test the fix and make sure it works, then report back to main agent.

    line 22
  4. Distinctive:

    If tests fail, repeat from step 2.

    line 23
  5. Distinctive:

    After finishing, respond back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest …

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fix Fast

Analyze the skills catalog and activate the skills that are needed for the task during the process.

Mission

Think hard to analyze and fix these issues: <issues>$ARGUMENTS</issues>

Workflow

For video/screenshot input handling, see workflows/visual-input.md. 2. Use debugger subagent to find the root cause of the issues and report back to main agent. 3. Work the issues one at a time: state the hypothesis, then the smallest change that tests it. 4. Start implementing the fix based the reports and solutions. 5. Use tester agent to test the fix and make sure it works, then report back to main agent. 6. If tests fail, repeat from step 2. Max 3 cycles — if still failing after 3, STOP and escalate (likely wrong approach, not the hypothesis); never loop indefinitely. 7. After finishing, respond back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free