GitHub
using-gambit
Use at session start - establishes mandatory workflows for finding and using skills
Veraticus AI Skills
GitHub ↗Explorez les skills IA publiés de Veraticus et consultez leurs instructions source.
Statistiques de l’auteur
Skills indexés
13Étoiles des dépôts des skills indexés
0Forks du dépôt
0Moyenne des étoiles par skill indexé
0Les étoiles d’un dépôt peuvent se répéter entre ses skills.
Catégories populaires
Indexation récente
Explorer
GitHub
executing-plans
Executes Tasks one at a time with mandatory human checkpoints. Reviews learnings, then STOPS for user review before continuing.
GitHub
task-refinement
Use when refining Tasks into actionable plans - SRE-style review ensuring corner cases handled, junior engineer can execute without questions
GitHub
finishing-branch
Use when implementation complete and tests pass - verifies all tasks done, presents integration options (merge/PR/keep/discard), executes choice
GitHub
refactoring
Use when improving code structure without changing behavior - test-preserving transformations in small steps, running tests between each change
GitHub
testing-quality
Use to audit test quality with SRE-level scrutiny - identifies tautological tests, coverage gaming, weak assertions, missing corner cases
GitHub
code-review
Use for requesting and receiving code reviews - dispatch reviewer agent for self-review, verify feedback before implementing, no performative agreement
GitHub
using-worktrees
Use when starting feature work that needs isolation - creates git worktrees with smart directory selection, safety verification, and environment setup
GitHub
brainstorming
Refines rough ideas into epic Tasks with immutable requirements through Socratic questioning. Use before any creative work.
GitHub
parallel-agents
Use when facing 3+ independent failures that can be investigated without shared state - dispatches multiple agents concurrently to investigate and fix problems in parallel
GitHub
test-driven-development
Use when implementing features or fixing bugs - enforces RED-GREEN-REFACTOR cycle requiring tests to fail before writing code
GitHub
verification
Use before claiming work complete, fixed, or passing - requires running verification commands and confirming output; evidence before assertions always
GitHub
debugging
Use when encountering bugs, test failures, or unexpected behavior - systematic root cause analysis before fixes, tools first, regression test required
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.