Session de QA interactive où l'utilisateur signale des bugs ou problèmes de manière conversationnelle, et l'agent crée des issues GitHub. Explore le codebase en arrière-plan pour le contexte et le langage métier. À utiliser lorsque l'utilisateur souhaite signaler des bugs, faire du QA, créer des issues de manière conversationnelle, ou mentionne « session QA ».
Cette skill transforme l'agent en un assistant de QA interactif. Elle permet à l'utilisateur de signaler des bugs ou problèmes de manière conversationnelle, sans avoir à remplir de formulaires complexes. L'agent explore automatiquement le codebase en arrière-plan pour comprendre le contexte, le langage métier et les conventions du projet. Il utilise ces informations pour formuler et créer des issues GitHub bien structurées, avec des titres clairs, des descriptions détaillées et des labels appropriés. La skill est conçue pour être utilisée sur n'importe quelle plateforme d'agent (Claude Code, Cursor, Codex, etc.) et ne nécessite aucune configuration spéciale. L'utilisateur peut simplement décrire le problème rencontré, et l'agent s'occupe du reste : recherche de code associé, reproduction des étapes, proposition de solutions potentielles, et finalement création de l'issue. Cela accélère considérablement le processus de signalement de bugs et améliore la qualité des rapports.
npx skills add https://github.com/mattpocock/skills/tree/main/skills/qaInstalled? Explore more Productivité et collaboration skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
Session de QA interactive où l'utilisateur signale des bugs ou problèmes de manière conversationnelle, et l'agent crée des issues GitHub. Explore le codebase en arrière-plan pour le contexte et le langage métier. À utiliser lorsque l'utilisateur souhaite signaler des bugs, faire du QA, créer des issues de manière conversationnelle, ou mentionne « session QA ».
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".
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
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.
Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.