All authors
Claude Skills by tatargabor
github.com/tatargabor23 skills0 installs30 views
- Agent CommTalking to the other agent sessions over set-agent-comm — reading the inbox, answering what is actually yours, declaring your scope so nobody has to ask, and arming the watch that wakes you when something needs you. Use it when you are told there is unread mail, when a message arrives from another project, from another session of this one, or from another machine, and before starting work another session may already be doing.Votes: 0GitHub stars: 35
- Cross Project ChannelThe TEMPORARY file channel between this project's session and a consumer project's session — where it lives, the append-only protocol, how to resume it after a compact or /clear, and how to check the Monitor and cron without creating duplicates. Use when coordinating with a consumer project's copilot, when resuming a session that was talking to one, or when a channel watch may have died.Votes: 0GitHub stars: 35
- E2e RunsHow to set up, start, compare and harvest end-to-end orchestration runs, and how to run the web dashboard's Playwright suite. Use when starting or supervising an E2E run, when reading a run log for framework bugs, when comparing two runs, or when the dashboard UI changed and its Playwright tests need running.Votes: 0GitHub stars: 35
- Evidence DisciplineThe worked cases behind this repo's evidence rules — every defect class with the measurement that found it, which way it failed, and the check that catches it, plus how to prove a fix is a fix (stash-and-rerun, asserting the mutation AND the restore, the .pyc trap, ambiguous mutation patterns). Use when a measurement looks surprising, when a green result seems too reassuring, when writing or reviewing a test meant to prove something, and when mutation-testing.Votes: 0GitHub stars: 35
- Openspec Apply ChangeImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.Votes: 0GitHub stars: 35
- Openspec Archive ChangeArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.Votes: 0GitHub stars: 35
- Openspec Bulk Archive ChangeArchive multiple completed changes at once. Use when archiving several parallel changes.Votes: 0GitHub stars: 35
- Openspec Continue ChangeContinue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.Votes: 0GitHub stars: 35
- Openspec ExploreEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.Votes: 0GitHub stars: 35
- Openspec Ff ChangeFast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.Votes: 0GitHub stars: 35
- Openspec New ChangeStart a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.Votes: 0GitHub stars: 35
- Openspec OnboardGuided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.Votes: 0GitHub stars: 35
- Openspec ProposePropose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.Votes: 0GitHub stars: 35
- Openspec Sync SpecsSync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.Votes: 0GitHub stars: 35
- Openspec Update ChangeUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.Votes: 0GitHub stars: 35
- Openspec Verify ChangeVerify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.Votes: 0GitHub stars: 35
- Regression BaselineHow to tell a real test regression from this repo's pre-existing failure debt — the set-diff against a baseline worktree, the three import roots and the session-end leak assertion that make the baseline an actual baseline, and why a stash inside a killable command must never be used. Use before claiming a test suite regressed or did not, and whenever comparing this working tree's failures against HEAD.Votes: 0GitHub stars: 35
- SetManage git worktrees for parallel AI agent development. Use this when asked to create, list, open, close, or merge worktrees, or when working with set-* commands.Votes: 0GitHub stars: 35
- DecomposeDecompose a specification document into an orchestration execution plan. **Input**: Spec file path (provided as argument or via environment `SPEC_PATH`), optional phase hint via `PHASE_HINT`. **You are a planning agent.** Your job is to analyze a spec document, explore the codebase, and produce an `orchestration-plan.json` that the orchestrator can dispatch.Votes: 0GitHub stars: 35
- ForensicsForensic analysis of a completed orchestration run. Use this for post-run debugging, error triage, and digging into what an agent actually did inside a session — without dragging raw 300 KB jsonl transcripts into context.Votes: 0GitHub stars: 35
- GlmRun Claude Code against the z.ai GLM models with the measured, working parameters — one-shot `-p` calls, batch loops, or an interactive session. Use when the user asks to run something on GLM, on a non-Anthropic model, or to compare models on the same task (an A/B run), and when a GLM run behaves strangely — silent stalls, "Prompt is too long", or a 400 on the model name. Carries the three failure modes measured in production so they do not have to be rediscovered.Votes: 0GitHub stars: 35
- HarvestHarvest framework fixes from consumer project E2E runs. **Input**: `--project <name>` (optional) — scan a single project. Without it, scans all registered consumer projects. **You are a framework maintainer.** Your job is to review ISS fixes and template changes from consumer E2E runs and decide which ones should be adopted into set-core.Votes: 0GitHub stars: 35
- Write SpecInteractive spec-writing assistant — guides users through creating a detailed, profile-driven specification. Detects project type, loads relevant sections from the profile system, enforces REQ-IDs and WHEN/THEN scenarios, generates modular output ready for orchestration.Votes: 0GitHub stars: 35