agentleFS
Sign inStart free
vishalguptaxvishalguptax/agent-engineering-kit/.claude/skills/quick-fix/SKILL.md

quick-fix

Skill0 starsChanged 24 days agoMITView on GitHub

Small, contained change or bug fix with a quick verify loop - when the change is clear and touches only a few files. Escalates to the feature workflow when it grows.

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the fix turns out bigger than step 1 suggested, stop and switch to the feature skill instead of growing the change.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “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

Quick fix

The change is what the user asked for when starting this skill. Follow the kit's rules, and for a bug also §9 of .agent-kit/RULES.md. The project's instructions (AGENTS.md, CLAUDE.md), including its Workflow Preferences section if there is one, take priority over the steps below.

  1. Size it first. Find the files the fix needs. If it needs more than about 6 files, more than 2 modules, a new dependency, or a design decision I haven't made, stop and say so: this belongs in the feature skill.
  2. Pin down the problem and decide what will prove the fix:
    • The project has tests: write a test that fails because of the bug (or that checks the new behavior), and watch it fail.
    • No test for this kind of code is possible or the project has no test setup: state the exact observable check instead (a command and its expected output, a request and its response, a screen and what it shows), and run it once to see the problem. Mention that a test would be worth adding; don't set up a test framework unasked.
  3. Make the smallest correct change. Match the surrounding style; touch nothing unrelated.
  4. Verify with the verify-change skill. The check from step 2 must now pass, and nothing else may break.
  5. Report in a few lines: the cause, the change, the evidence, and anything not verified. Don't commit unless I ask (the ship skill).

If the fix turns out bigger than step 1 suggested, stop and switch to the feature skill instead of growing the change.

Download now (ZIP)

  • Other versions13 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 13

    1. gittower/git-flow-next★ 458same name
    2. danielvm-git/bigpowers★ 286same name
    3. charliehzm/medharness★ 85same name
    4. DailybotHQ/deepworkplan-website★ 15same name
    5. jasonmichaelbell78-creator/sonash-v0★ 2same name
    6. sumulige/sumulige-claude★ 2same name
    7. iabhisekbosepm/claude-god-setup★ 1same name
    8. Nexus-Organization-Infosec/ClaudeSkills★ 1same name
    9. SgtPooki/skills★ 1same name
    10. acevinh/claude-skills★ 0same name

    3 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use security-review.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • SentrySkill

      security-review

      Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.

      Also in 3 projects that use this

  • In this repository8 other files it gives its agents.

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