agentleFS
Bossmann007Bossmann007/cursor-kit/skills/blindspot-pass/SKILL.md

blindspot-pass

Skill0 starsChanged 55 days agoMITView on GitHub

Second-pass review for missed edge cases, security, and silent failures before shipping. Use after the main fix/feature looks done, or when the user says blindspot, second pass, or what did we miss. Complements verification-planning (evidence path before/during) — do not invent scope.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    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:

    After the main fix/feature looks done:

    line 13
  2. Distinctive:

    Check error paths, empty inputs, auth / trust boundaries

    line 19

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

Blindspot pass

After the main fix/feature looks done:

  1. Confirm the evidence path from /verification-planning (or checkpoint tests) was run with fresh results — if no path exists for non-trivial work, draft one first
  2. List assumptions that were not verified
  3. Check error paths, empty inputs, auth / trust boundaries
  4. Confirm tests cover the failure mode, not only the happy path
  5. Fix only real gaps; do not invent scope

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.