agentleFS
fqmyysjjdfqmyysjjd/agent-feed/.agents/skills/project-fix/SKILL.md

project-fix

Skill4 starsChanged 6 months agoMITView on GitHub

Use when fixing bugs, review findings, regressions, failed tests, merge issues, contract drift, or behavior defects.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for bug fixes, review finding fixes, regression fixes, failed test fixes, merge conflict aftermath, contract drift, or …

    line 12
  2. Very specific:

    Use .agents/skills/engineering-planning/SKILL.md to decide owner, reuse, placement, write set, boundaries, and verification before editing.

    line 27
  3. Distinctive:

    Add or update tests that would fail before the fix and pass after it when practical.

    line 32
  4. Distinctive:

    Stop when the declared fix boundary is satisfied.

    line 34

≈ “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

Project Fix Skill

Required Use

Use this skill for bug fixes, review finding fixes, regression fixes, failed test fixes, merge conflict aftermath, contract drift, or behavior inconsistencies.

Required Reading

  1. .agents/rules/outcome-boundary.md
  2. .agents/skills/project-architecture/SKILL.md
  3. .agents/skills/engineering-planning/SKILL.md
  4. .agents/skills/project-development/SKILL.md
  5. .agents/rules/review-gates.md
  6. .agents/rules/testing-gates.md
  7. .agents/domain/contracts.md

Workflow

  1. Recover the current task result boundary.
  2. Use .agents/skills/engineering-planning/SKILL.md to decide owner, reuse, placement, write set, boundaries, and verification before editing.
  3. Intake symptom, expected behavior, current behavior, changed files, and affected phase.
  4. Reproduce or trace the issue.
  5. Locate the root cause and owner module.
  6. Apply the smallest fix that preserves boundaries and source-of-truth ownership.
  7. Add or update tests that would fail before the fix and pass after it when practical.
  8. Run relevant verification.
  9. Stop when the declared fix boundary is satisfied.

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.