agentleFS
irahardiantoirahardianto/awesome-agv/.agents/skills/bugfix/SKILL.md

bugfix

Skill157 starsChanged 32 days agoMITView on GitHub

Fixes bugs of any size from hotfixes to complex debugging sessions using root cause diagnosis and TDD. User-invoked entry point via /bugfix; not for autonomous or subagent use.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use feature, spec and 7 more.

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.
  • bradtraversySkill

    feature

    Manage current feature workflow - start, review, explain or complete

    Also in 7 projects that use this

  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 4 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 8 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    docs

    Also in 3 projects that use this

  • MicrosoftSkill

    pr-review

    Verify the technical accuracy of a vscode-docs pull request against the VS Code source code in microsoft/vscode. Use when reviewing a docs PR for factual correctness: setting names, command IDs, default values, API shapes, keybindings, versioned availability, and described behavior.

    Also in 3 projects that use this

  • +1 more from getsentry

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 5 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before starting, you MUST:

    line 28
  2. Very specific:

    Read rule-priority.md for conflict resolution

    line 30
  3. Very specific:

    Set Mode: Use task_boundary to set mode to PLANNING

    line 35
  4. Distinctive:

    If the cause is not immediately obvious, activate the Debugging Protocol skill

    line 39
  5. Very specific:

    Set Mode: Use task_boundary to set mode to EXECUTION

    line 48
  6. Distinctive:

    If the fix touches integration boundaries (database queries, API calls, external services), write or update integration tests

    line 53
  7. Very specific:

    Set Mode: Use task_boundary to set mode to VERIFICATION

    line 59
  8. Distinctive:

    Run the full validation suite: quality checks per idiom skill, all tests, build check

    line 61
  9. Very specific:

    If the fix touched UI or user-facing flows, run E2E validation per browser-automation skill

    line 62
  10. Distinctive:

    If all checks pass, commit with conventional format per @git-workflow-principles.md

    line 63
  11. Very specific:

    Use commit type fix(<scope>): <description>

    line 64

“Common” is measured: kept by at least 6 in 10 of the 32 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

Bug-Fix Skill

Entry-point guard: This is a user-invoked command skill (/bugfix). If you are a spawned subagent, do NOT execute this skill — return to your assigned scope card.

Purpose

Fix bugs of any size — from one-line hotfixes to multi-file debugging sessions — without the overhead of a full feature workflow.

When to Use

  • Bug fixes (any size, any complexity)
  • Hotfixes for production issues
  • Addressing review findings from /audit
  • Regression fixes after deployments
  • Flaky test fixes

When NOT to Use

  • New features (use /workflow-solo)
  • Refactoring (use /refactor)
  • Code quality audits (use /audit)

Pre-Implementation Checklist

Before starting, you MUST:

  1. Scan .agents/rules/ directory for applicable rules
  2. Read rule-priority.md for conflict resolution

Phases

Phase 1: Diagnose

Set Mode: Use task_boundary to set mode to PLANNING

  1. Identify the bug or issue
  2. Locate the affected code — trace from symptoms to root cause
  3. If the cause is not immediately obvious, activate the Debugging Protocol skill
  4. Assess blast radius — which files, features, and tests are affected?
  5. Define the fix in task.md

Skills to consider:

  • Debugging Protocol — for non-obvious root causes, flaky tests, or multi-component bugs
  • Sequential Thinking — when multiple hypotheses need systematic evaluation

Phase 2: Fix + Test (TDD)

Set Mode: Use task_boundary to set mode to EXECUTION

  1. Write a failing test that reproduces the bug
  2. Apply the fix to make the test pass
  3. Verify existing tests still pass
  4. If the fix touches integration boundaries (database queries, API calls, external services), write or update integration tests
  5. Follow applicable rules:
    • Error Handling Principles @error-handling-principles.md
    • Logging and Observability Mandate @logging-and-observability-mandate.md

Phase 3: Verify + Ship

Set Mode: Use task_boundary to set mode to VERIFICATION

  1. Run the full validation suite: quality checks per idiom skill, all tests, build check
  2. If the fix touched UI or user-facing flows, run E2E validation per browser-automation skill
  3. If all checks pass, commit with conventional format per @git-workflow-principles.md
  4. Use commit type fix(<scope>): <description>

Completion Criteria

  • Root cause identified and documented
  • Bug reproduced with a test
  • Fix applied and test passes
  • Integration tests updated (if applicable)
  • Full verification suite passes
  • Committed with fix type

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.