Menu
SkillsMP a collecté 28 skills depuis scheron/dotfiles. Ouvrez un skill pour examiner sa source et ses détails.
Affichage de 28 skills collectés sur 28.
Daily is the user's personal task tracker; the `daily` CLI reads and changes its tasks. Use when the user names Daily about tasks (also spelled "дейли"), asks about their own day or to-dos without naming it ("what do I have today", "what was I doing on…
Langue du texte source : anglais
Столкнуть Claude Code и Codex — две модели разных провайдеров — в споре по одной теме, до согласованного решения или эскалации человеку. Use when the user wants a second opinion from a different provider, a cross-model debate, or to stress-test a design…
Langue du texte source : russe
Russian ultra-compressed communication mode based on JuliusBrussee/caveman PR #144. Cuts token usage by answering in terse Russian while keeping full technical accuracy. Supports ru-lite, ru-full default, ru-ultra, and ru-notes. Use when user says caveman-ru,…
Langue du texte source : Plusieurs langues
Run a batch of already-cut tickets through the /to-implement engine UNATTENDED, in dependency order — one fresh headless session per ticket, advancing on green, halting on the first red. The automation layer over /to-tickets → /to-implement: instead of…
Langue du texte source : anglais
Write the closed technical execution contract for one unit at pickup, inside the unit's worktree — cutting the ticket's vertical slice into horizontal tasks, each with its files, declared interfaces, fence and proof. For the brief-writer subagent the engine…
Langue du texte source : anglais
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…
Langue du texte source : anglais
Read a finished spec and its tickets from the position the brief-writer will occupy — no planning context — and report what was understood. Surfaces drift between what you meant and what the artifact says, while fixing is still free. Use after /to-tickets and…
Langue du texte source : anglais
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple…
Langue du texte source : anglais
Materialise a scout's open decisions as decision tickets and burn them down — research in parallel, prototypes for runnable questions, grills for the user's calls — until the fog clears and the normal chain can start. Use when the open decisions exceed one…
Langue du texte source : anglais
Diagnosis loop for hard bugs and performance regressions — feedback loop first, then reproduce, minimise, pattern-analyse, rank hypotheses, instrument, fix. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Langue du texte source : anglais
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.
Langue du texte source : anglais
Complete development work — harvest durable knowledge into ADRs and CONTEXT.md, verify the build, present integration options, execute the choice, and clean up the worktree and .scratch/. Use when implementation is complete and tests pass.
Langue du texte source : anglais
A relentless interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as we go. It is /grill plus /domain-modeling.
Langue du texte source : anglais
Grill the user relentlessly about a plan, decision, or idea — a lightweight interview that writes no docs. Use for stress-testing thinking inline, or on any 'grill' trigger; for a feature grill that also writes CONTEXT.md and ADRs, use /grill-me.
Langue du texte source : anglais
Compact the current conversation into a handoff document for another agent to pick up.
Langue du texte source : anglais
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Langue du texte source : anglais
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Langue du texte source : anglais
Use when you need to resolve an in-progress git merge/rebase conflict.
Langue du texte source : anglais
The entry point to the dev-stack — scouts a task read-only, proposes one of two tiers from the evidence, and routes into a driver behind your go. Use when unsure which tier or flow fits a task, or type /route-me any time to reprint the map and cheat sheet.
Langue du texte source : anglais
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Langue du texte source : anglais
The Tier 1 driver — one vertical slice, run as a single unit through the engine: a bug fix, a small feature, or a small refactor. Use when the user types /tier-1 already knowing the tier, or when route-me proposes Tier 1 and the user approves. Bug-shaped work…
Langue du texte source : anglais
The Tier 2 driver — work that is more than one vertical slice, driven through the planning chain (grill, spec, tickets, cold read) and then built as several Tier 1 units, one ticket at a time. Use when the user types /tier-2 already knowing the tier, or when…
Langue du texte source : anglais
The execution engine — runs ONE unit (an approved chat plan, a raw task, a single-slice spec, or one ticket) through its full lifecycle in an isolated worktree: ready-check, brief, verify-brief, waves of implementer+reviewer pairs, slice review, ADR,…
Langue du texte source : anglais
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Langue du texte source : anglais
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Langue du texte source : anglais
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Langue du texte source : anglais
Review the finished slice against a fixed point: the unit's only full sweep, then the real runtime driven and observed, then two axes — Standards (what only the assembled slice can show — duplication across tasks, seams that don't fit) and Spec (does it match…
Langue du texte source : anglais
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Langue du texte source : anglais