agentleFS
Sign inStart free
ultimatileultimatile/development-skills/skills/gate-miss-to-issue/SKILL.md

gate-miss-to-issue

Skill0 starsChanged 33 days agoMITView on GitHub

Promote a late-caught defect — one an earlier gate should have caught — into a development-skills issue proposing a fix to that gate's procedure.

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. Very specific:

    Don't edit the gate's SKILL.md inline.

    line 19
  2. Distinctive:

    Don't file for a one-off execution lapse the gate already covers — only for a generalizable procedure gap.

    line 20
  3. Distinctive:

    Don't propose a code change here.

    line 21
  4. Distinctive:

    Don't recurse: this skill has no gate of its own to postmortem.

    line 22

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

Gate-Miss-to-Issue

A gate's failure is invisible to the gates downstream of it — they judge the product, not which earlier step should have caught the defect. This skill captures that gap as a development-skills issue.

Do

  • Propose which gate should have caught it — skill + step, or no existing gate if none owns the class. This is a hypothesis the issue confirms or redirects, not a blame verdict.
  • State the blind spot as a general class, not the one token that slipped.
  • File the proposal as an issue against ultimatile/development-skills, via file-issue, with the four points below.
  • On recurrence of a class that already has an open issue, comment on it instead of filing a duplicate.

Don't

  • Don't edit the gate's SKILL.md inline. File an issue; the fix is deliberated async so the work-repo PR that surfaced the miss is not blocked.
  • Don't file for a one-off execution lapse the gate already covers — only for a generalizable procedure gap.
  • Don't propose a code change here.
  • Don't recurse: this skill has no gate of its own to postmortem.

Issue content

Hand file-issue these four points:

  • Gate (proposed) — the skill + step you argue should have caught it, or none yet.
  • Miss — the defect, and where it was finally caught; link the work-repo PR / issue for provenance.
  • Blind spot — the generalizable procedure gap.
  • Proposed improvement — a concrete procedure change (a new sweep, a tightened definition, an added probe class).

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