bulma-triage
Skill1 starsChanged 50 days agoMITView on GitHub
Graph: investigate a QA failure, classify PR_BUG / EXISTING_BUG / NEW_BUG / NOT_A_BUG / BLOCKED, route via the bus. Use when /bulma-triage, or a TRIAGE_REQUEST envelope arrives.
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/bulma-feature-delivery/adapters/claude.mdCLAUDE.md
- architectSkill
- before-and-afterSkill
- blast-radiusSkill
- bulma-busSkill
- bulma-code-reviewSkill
- bulma-developerSkill
- bulma-fdSkill
- bulma-feature-deliverySkill
- bulma-goalSkill
- bulma-hostSkill
- bulma-lstmSkill
- bulma-memorySkill
- bulma-qaSkill
- bulma-reviewerSkill
- bulmaSkill
- diagnoseSkill
- figure-it-outSkill
- grill-with-docsSkill
- howSkill
- interrogateSkill
- kevinSkill
- no-commentsSkill
- principle-fix-root-causesSkill
- principle-prove-it-worksSkill
- principle-sequence-verifiable-unitsSkill
- receiving-code-reviewSkill
- tddSkill
- technical-writingSkill
- thermo-nuclear-code-quality-reviewSkill
- to-issuesSkill
- to-prdSkill
- typescript-best-practicesSkill
- unslopSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 14
Not a ticket bot. Use the session model.
≈ “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.
Files
Bug Triage (graph)
Orchestrator. Investigate first. Decide second. Act third. Not a ticket bot. Use the session model; high effort if the host exposes it (bulma-host).
REQUIRED: GRAPH.md · STATE.schema.md ·
bus PROTOCOL.md · bulma-memory ·
DISK.md (.bulma-* is global, never git root)
Chat: bulma-memory. Apply Kevin for human-facing communication. PR link required. Init .bulma-triage/STATE.md. Walk GRAPH.
Classify each finding. NEW_BUG → tracker issue (LINEAR.md).
PR_BUG → TRIAGE_RESULT + pop to QA. Do not switch to
developer. Do not spawn bulma_developer.
Not bulma-fd-triage (that router picks fd paths).
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
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.