agentleFS
Sign inStart free
JustineDevsJustineDevs/meta-architect/skills/diagnose/SKILL.md

diagnose

Skill5 starsChanged 7 months agoMITView on GitHub

Use when the user needs failure triage, blocked-lane diagnosis, or root-cause decomposition before the next gate can move.

193 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use zoom-out, to-prd and 10 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.
  • victorgarciaesgiSkill

    zoom-out

    Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.

    Also in 61 projects that use this

  • GoogleSkill

    to-prd

    Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    Also in 56 projects that use this

  • GoogleSkill

    to-issues

    Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

    Also in 53 projects that use this

  • simo97Skill

    edit-article

    The user will invoke this skill to help them edit an article.

    Also in 17 projects that use this

  • simo97Skill

    write-a-skill

    Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.

    Also in 44 projects that use this

  • AnasX7Skill

    setup-pre-commit

    Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

    Also in 27 projects that use this

  • +4 more from simo97

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 174 edited versions we read keep these.

  • 5

    Distinctive

    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:

    Use this skill inside Codex when a lane is blocked, a symptom is vague, or the next useful move is to decompose the failure before editing …

    line 8
  2. Distinctive:

    Prefer the smallest reproducible boundary that can confirm or kill a hypothesis.

    line 22
  3. Distinctive:

    Keep release-state ownership with the gated lane that is blocked.

    line 23
  4. Distinctive:

    Run the smallest read-only probe that distinguishes the leading hypotheses.

    line 30
  5. Distinctive:

    Never infer success from a stale UI state, cached artifact, or unverified deployment.

    line 37
  6. Distinctive:

    If evidence is insufficient, state the next probe instead of inventing certainty.

    line 38

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

Diagnose

Use this skill inside Codex when a lane is blocked, a symptom is vague, or the next useful move is to decompose the failure before editing code. diagnose is a non-gating helper skill.

Output

Produce:

  • observed symptom
  • likely failure slices
  • missing evidence or missing reproduction steps
  • smallest next probe
  • exact next trigger, usually the owning lane or $maestro

Rules

  • Decompose the problem before proposing broad fixes.
  • Prefer the smallest reproducible boundary that can confirm or kill a hypothesis.
  • Keep release-state ownership with the gated lane that is blocked.
  • Escalate assumptions clearly when evidence is still incomplete.

Procedure

  1. Restate the observed symptom, expected behavior, scope, and first failing boundary.
  2. Build a short hypothesis tree ordered by likelihood and impact.
  3. Run the smallest read-only probe that distinguishes the leading hypotheses.
  4. Record exact evidence, including versions, routes, inputs, and failure output.
  5. Recommend one repair owner and one verification step; do not make unrelated edits.

Quality bar

  • Separate a symptom from a root cause and a contributing condition.
  • Never infer success from a stale UI state, cached artifact, or unverified deployment.
  • If evidence is insufficient, state the next probe instead of inventing certainty.

Example

For a plugin skill marked “Error,” inspect the archive root, manifest, skill path, front matter, and server discovery separately before changing the skill text.

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