Boucle de diagnostic disciplinée pour les bugs complexes et les régressions de performance. Reproduire → minimiser → hypothèse → instrumenter → corriger → test de régression. À utiliser lorsque l'utilisateur dit « diagnostique ceci » / « débogue ceci », signale un bug, indique que quelque chose est cassé/qui jette une erreur/qui échoue, ou décrit une régression de performance.
La compétence mattpocock/diagnose fournit un protocole structuré et itératif pour aborder les bugs difficiles et les régressions de performance. Elle guide l'utilisateur à travers six étapes clés : reproduire le problème de manière fiable, minimiser la cause possible, émettre une hypothèse sur la cause racine, instrumenter le code avec des logs ou des métriques, appliquer un correctif, puis mettre en place un test de régression pour éviter que le problème ne se reproduise. Cette approche disciplinée est particulièrement utile lorsque l'utilisateur dit « diagnostique ceci » / « débogue ceci », signale un bug, mentionne que quelque chose est cassé, qui jette une erreur ou qui échoue, ou encore lorsqu'il décrit une régression de performance. La compétence est conçue pour fonctionner avec des agents basés sur Claude Code, Cursor, Codex, et d'autres outils d'IA de développement, en s'appuyant sur une documentation standardisée (SKILL.md) pour guider l'agent dans l'exécution d'un diagnostic méthodique.
npx skills add https://github.com/mattpocock/skills/tree/main/skills/diagnoseInstalled? Explore more Développement et programmation skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →
Boucle de diagnostic disciplinée pour les bugs complexes et les régressions de performance. Reproduire → minimiser → hypothèse → instrumenter → corriger → test de régression. À utiliser lorsque l'utilisateur dit « diagnostique ceci » / « débogue ceci », signale un bug, indique que quelque chose est cassé/qui jette une erreur/qui échoue, ou décrit une régression de performance.
This repo contains 20 individual skills — each has its own dedicated page.
Ask which skill or flow fits your situation. A router over the skills in this repo.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Compact the current conversation into a handoff document for another agent to pick up.
Implement a piece of work based on a PRD or set of issues.
Implement a specification in code.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Grill me about specs for the workflows I want to build, within this workspace.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Send and manage iMessages via BlueBubbles, including attachments, tapbacks, edits, replies, and groups.
Control Eight Sleep pods (status, temperature, alarms, schedules).
BluOS CLI (blu) for discovery, playback, grouping, and volume.
Create, search, and manage Bear notes via grizzly CLI.
Capture frames or clips from RTSP/ONVIF cameras.
Search GIF providers with CLI/TUI, download results, and extract stills/sheets.