taxasge-gono-go-validator
Orchestre agents TEST/DOC pour validation tâche, calcule score /100, génère 3 rapports, commit auto
Discover Documentation skills, compare source repositories and read the instructions for each workflow.
Orchestre agents TEST/DOC pour validation tâche, calcule score /100, génère 3 rapports, commit auto
Create new Sandestin effect registries following project conventions. Use when adding effects, actions, or placeholders. Keywords: registry, effect, action, placeholder, handler, create, new.
Set up Sandestin in a new project. Use when integrating sandestin into an application or library, creating dispatch namespaces, or wiring registries together. Keywords: setup, bootstrap, create-dispatch, wire,...
Discover available effects, actions, and placeholders in a Sandestin project. Use when asking what effects exist, searching for functionality, or needing example invocations. Keywords: effects, actions, dispatc...
Use when working with MCP servers for enhanced capabilities like documentation retrieval, database access, or specialized tools. Triggers - mcp, context7, documentation lookup, external docs.
Use when creating or updating rules in CLAUDE.md, settings, or rule files. Covers confidence thresholds and false positive prevention.
Efficient handling of long-running commands. Use when running tests, builds, or any command that takes more than a few seconds. Prevents token waste from polling.
Create a Linear Project from requirements using Discovery Mode brainstorming. Same process as /spec but outputs to Linear instead of file. Triggers - linear spec, spec to linear, create project from spec, linea...
Review and clean up the Linear backlog. Close stale issues, update priorities, merge duplicates, request clarification. Triggers - backlog grooming, backlog cleanup, groom backlog.
Fix Linear issues tagged with "bug". Either produces a PR with the fix or explains why it won't be fixed. Triggers - fix bugs, linear bugs, bug triage, resolve bugs.
Use when encountering bugs, test failures, or unexpected behavior. Hypothesis-driven debugging.
Use for complex features requiring multi-stage review, architectural work, or multi-file changes. Orchestrates specialized agents for coordinated implementation.
Answer Linear issues tagged with "question". Explores codebase and produces decisions - never code changes or PRs. Triggers - answer questions, linear questions, question triage.
Use when creating PRs, managing stacked PRs, or completing feature branches.
Use when making commits. Conventional commits, atomic changes.
Supabase client setup, Row Level Security (RLS), edge functions, and real-time. Use when working with Supabase database, auth, or edge functions.
Use when creating slash commands, user-invokable shortcuts, or command-based workflows with frontmatter and skill delegation.
Review Linear issues tagged with "feature-request". Decide to spec, add to roadmap, merge, or reject. Triggers - review feature request, user request, customer feedback.
React component patterns, hooks, server components, and composition. Use when building React components or deciding between patterns.
Use when reviewing code changes or conducting PR reviews.
Next.js App Router patterns, server actions, caching, and routing. Use when working with Next.js 14+ features.
Create a Linear Document with technical design using Approach Mode brainstorming. Same process as /brainstorm how, outputs to Linear Document. Triggers - linear design, design to linear, technical design, archi...
Generate health report for a Linear project. Progress vs plan, blocked issues, overdue items, risk assessment. Triggers - project health, project status, project report.
Use when creating or updating CLAUDE.md files at any level (global, project, folder). Covers inheritance rules and token budgets.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.