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

vk-fix

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

⚡⚡ Analyze and fix small issues [AUTO DETECT COMPLEXITY]

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    If there is a markdown implementation plan already, use /vk-cook <path-to-plan> [--no-hoh] slash command to implement it.

    line 9
  2. Very specific:

    Read only workflows/routing-card.md to decide fast vs hard.

    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

If there is a markdown implementation plan already, use /vk-cook <path-to-plan> [--no-hoh] slash command to implement it. /vk-cook delegates the HoH continual-improvement loop by default (step 4); pass --no-hoh to opt out to legacy cook-worker execution. --no-hoh/--loops forward through cook.

Else:

  • Analyze the issues and ask for more details if needed.
  • Route by the SHAPE of the issue first, complexity second:
RouteWhen
/vk-fix-source <input>there is a concrete failure source: a CI/GitHub-Actions URL, a log file (./logs.txt), or a test suite to run. Add --plan-only to stop at the plan.
/vk-fix-typesthe issue is type/compile errors from tsc/typecheck
/vk-fix-ui <issue>the issue is visual/UI/design-guideline drift
/vk-fix-fast <prompt>no such source, and the Complexity Rubric §1 in workflows/routing-card.md says fast (<2 "hard" signals)
/vk-fix-hard <prompt>no such source, and the Rubric hits ≥2 "hard" signals
  • Read only workflows/routing-card.md to decide fast vs hard. Ambiguous → ask one clarifying question.

Fix loop vs HoH

/vk-fix-fast, /vk-fix-hard, /vk-fix-source carry their own debugger→fix→tester 3-cycle loop — they do NOT invoke HoH. HoH (continual improvement) targets greenfield/incremental development; fixing a reported bug is a root-cause diagnosis that the fix loop already handles efficiently. Only /vk-fix delegating to /vk-cook (when a plan already exists) inherits the HoH default — the rest stay in their own fix loop. Do not route fix paths through HoH unless the user explicitly asks.

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.

Reviews can't be read right now.

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