All authors
Claude Skills by Arasz
github.com/Arasz66 skills0 installs0 views
- Research Record AuditUse when auditing a research record's factual accuracy, citation truth, or grade correctness: adversarially re-derive every load-bearing claim from cited sources, verify quotes verbatim at cited lines, re-run MEASURED claims, audit grade honesty (INFERRED hedged, UNVERIFIED plain), check negative claims for prune/retention explanations, and report ACCURATE/CORRECTED/OVERCLAIMED.Votes: 0GitHub stars: 2
- Review ChangesUse when reviewing a diff, PR, or a batch of changed files and you need to know where the risk concentrates — which changed units have the largest blast radius, whether the highest-risk ones are actually covered by tests, and whether the result is safe to merge. Trigger phrases: "review these changes", "how risky is this diff", "what's the blast radius", "did anything untested change", "rank these changes by risk". Not for a pass/fail preflight of style, security, and layering checks — that i...Votes: 0GitHub stars: 2
- Review Gate Diff VerificationUse when a review gate judges a branch diff: verify the diff base FIRST — merge-base vs moved origin/main ref (phantom D/M files), grep anchors after the status tab, exclude bin/obj from symbol greps, and diff the committed plan against the accepted amended version before judging implementation.Votes: 0GitHub stars: 2
- Review TestsUse when tests that already exist have to be judged rather than written — "are these tests any good", "review the tests in this PR", "why did the suite stay green while that shipped", a coverage number nobody trusts, a gate nobody has watched fail, a lane that flakes, or a test file a reviewer flagged. Takes a directory, a file list, a diff, or "the tests for X"; refuses to run with no target. Returns findings, not edits.Votes: 0GitHub stars: 2
- Scripts Tooling RefactorUse when refactoring a repo's scripts/ directory: convert non-python scripts to the repo's tooling language, move logic to src/ with tests in tests/ (TDD first), prune dead scripts on usage evidence (git ls-files inventory, LIVE/HISTORICAL classification, three-way sync contracts), and preserve call sites with thin wrappers.Votes: 0GitHub stars: 2
- Semantica Knowledge GraphUse when reasoning over structured project knowledge — record decisions with provenance, trace causal chains, extract entities from conversations, or run graph analytics. Complements AiRaccoon memory (recall) with structured reasoning (connections and causality).Votes: 0GitHub stars: 2
- Send MessageUse when an agent session needs to reach another agent session, every session in a project, or every session on this machine without the human relaying between windows — 1:1, project-broadcast and machine-broadcast sends through the machine-wide user-DB message bus.Votes: 0GitHub stars: 2
- Spec Driven RefactoringUse when the user says 'refactor', 'migrate', or 'rename across the codebase', or a change touches 5+ files across schemas, scripts, tests, and docs: write a spec, run two review gates (pre-implementation consistency + post-implementation quality), then implement against it. Covers schema migrations, concept renames, structural reorganizations.Votes: 0GitHub stars: 2
- Status ReportUse when the user asks where things stand mid-task — "status", "status report", "where are we", "what's the current task", "task progress", "what's next", "subagent status", "is the delegation done" — or wants a progress snapshot while work is still running. Answers NOW from the /task tracking files: current task, progress as a checklist, what is next, and sub-agent/delegation status. Important by default: never deferred to task end, never delegated, never turned into analysis.Votes: 0GitHub stars: 2
- Task DecompositionUse when a researched task must become an executable plan — "decompose this", "split this into steps", "turn the research into a plan". Turns a brief into a `task-plan`: a DAG of steps with acceptance criteria, dependencies, effort and owned files; records it through the `task-graph` server (or its CLI twin), re-authors it when review finds defects, and names the join rule and the no-server fallback. `task` runs this in its plan phase; `quick-task` never does.Votes: 0GitHub stars: 2
- TaskUse when the user wants to start, continue, or finish a backlog task — "/task <id>", "start task X", "work on the next task", "finish this task". Runs it end-to-end as a token-tracked unit of work with low/high effort, `task-decomposition` into a `task-plan` whose `workflow` is a DAG of `step`s, MoE panels for high-effort, and automated task-ID derivation ({repo-alias}-{key}). Delegates planning/review to high-reasoning models and implementation to persona-routed agents. Project specifics fro...Votes: 0GitHub stars: 2
- Test EconomyUse when a change's tests are about to run — deciding what to run locally (the modified surface and its consumers, once), what to leave to CI (the full suite, when CI is alive), and what to do when CI is dead (hooked-up local gates once, else one manual full-suite run before push) — or when full-suite runs start repeating and something must say stop. A PostToolUse hook counts shell test-runner commands, classifies full vs filtered, and commands the economy on the run past the session's budget...Votes: 0GitHub stars: 2
- Welcome Ai BadgerUse when a repository should be set up with ai-badger — "welcome-ai-badger", "scaffold this project", "add agent instructions here", "onboard this repo" — whether it is new or already has agent files. Detects stacks, writes .ai-badger/, and generates each configured agent's discovery file.Votes: 0GitHub stars: 2
- Worktree Agent IsolationUse when running multiple agents in parallel, or when the user says 'worktrees only', 'agent isolation', 'parallel workstreams', or 'don't touch main': give each agent its own git worktree branched from origin/main (fetch first), integrate via GitHub PRs, keep the main checkout read-only, and avoid shared obj/ races and file-modification conflicts.Votes: 0GitHub stars: 2
- Decision RecordUse when a change adds a feature or meaningfully changes how something works and the decision behind it has to be written down before implementation — "record this decision", "write an ADR", "open a spec change", "decision record", or the task skill's decision-record step. Detects what the project already uses (an ADR log in MADR, adr-tools or log4brains shape; OpenSpec, Spec Kit or Kiro specs; the CLIs on PATH), writes into that format, and writes a linked ADR-plus-spec pair when the project...Votes: 0GitHub stars: 2
- Simplified Technical EnglishUse when writing anything the user reads — a response, an answer, a final report, a status update, a question, a decision request, a warning, step-by-step instructions, or a subagent hand-back. Applies the ASD-STE100 Simplified Technical English writing rules to user-agent communication, including readers whose first language is not English.Votes: 0GitHub stars: 2