All authors
Claude Skills by Arasz
github.com/Arasz66 skills0 installs0 views
- Ai Raccoon MemoryUse when a project needs a memory server — search project and shared memory first, write durable facts with source paths, watch a docs directory, or promote facts across projects.Votes: 0GitHub stars: 2
- ArchifyUse when the user asks to visualize system architecture, infrastructure, cloud/security topology, technical workflows, API call sequences, request lifecycles, data pipelines or state machines — or to convert/beautify a Mermaid diagram — as a polished standalone HTML diagram. Archify is the default for committed architecture, workflow, sequence, data-flow, and lifecycle deliverables; fall back to Mermaid when Node.js 18+ or the skill is unavailable, when the diagram must render inline in commi...Votes: 0GitHub stars: 2
- Artifact VerificationUse when verifying changed artifacts that lack a canonical test gate — specs, docs, manifests, generated files, published packages: use the workflow-defined checker first (spec_holes.py), review manual fresh-install protocols against the false-pass checklist, and verify 'installed build contains merged PR X' by tree comparison, never squash-ancestry.Votes: 0GitHub stars: 2
- Browser UsageUse when interacting with web pages, running manual E2E browser tests, testing UI flows, or inspecting live web surfaces via Playwright MCP. Employs text-first accessibility snapshots and element refs, network inspection, form filling, and custom Playwright script execution.Votes: 0GitHub stars: 2
- Call BehavioristUse when ai-badger's own machinery needs to be observed — "did that hook even run?", "enable debug logging", "why is the drift notice silent?", "turn on the audit log", "what did the hooks do?" — or to check, tail, or switch off that logging. Records which hook ran, in which project, under which version, to an append-only log.Votes: 0GitHub stars: 2
- ChangeUse when making an ad-hoc change with no issue or task behind it — fix a failing unit test, refactor a method, rename something, tweak a config value, adjust one behavior, "quick one", "just change X", "small update" — any edit to the project's state that has a distinct, small, limited scope and is not a tracked backlog task. Applies even when the request says "no ceremony" or "just do it".Votes: 0GitHub stars: 2
- Code Review ChecklistUse when reviewing code — a PR, a diff, or freshly written changes — and you want concrete pass/fail checks rather than impressions. An aviation-style preflight checklist organised into sequential phases, with stack-specific items merged in from the project's config.Votes: 0GitHub stars: 2
- Code Review EvidenceUse when reviewing code that wraps external libs/extensions/SDKs/CLIs, or QA-reviewing a test harness: verify wrapped-library semantics from the upstream source (not comments/spec), query the real store read-only for data claims, and hunt tautological tests that assert values the code constructed itself. Catches spec-vs-coverage gaps, fake honesty, hygiene.Votes: 0GitHub stars: 2
- Code ReviewUse when performing a code review in this repository — reviewing a pull request, a branch diff, or a requested re-review. This is the review entry point GitHub Copilot code review loads from .github/skills/ (a review-focused skill name and description, as GitHub's docs recommend); it routes to the deeper review skills this project ships — risk ranking, pass/fail gates, test-quality judgement, whole-project review — adjusted per project stack. Trigger phrases: "review this PR", "review these c...Votes: 0GitHub stars: 2
- Commit ReminderUse when a project has accumulated uncommitted changes and nobody has said so out loud — several edits in a row with no commit in between — or when a subagent may be stuck and about to lose its work ("did that agent commit?", "is anything at risk?", "ensure work is committed"). A PostToolUse hook watches the live `git status --porcelain` count after every edit-shaped tool call and commands a commit once it crosses a threshold; after repeated unanswered commands it records the work as at risk,...Votes: 0GitHub stars: 2
- Complete Project Scope Code ReviewUse when the whole project — not a diff — is the review target and the result must survive being acted on: "review the entire codebase", "full quality review", "MoE review", "what is wrong with this project", "audit everything before the next release", or a review whose findings will become a plan someone implements. Runs ground-truth baseline, parallel expert lanes, integration, an adversarial pass that tries to falsify the findings, severity calibration against production reality, a reviewe...Votes: 0GitHub stars: 2
- Create Task SpecUse when a feature idea needs to become an exact, agreed specification before anyone builds it — "spec this out", "create a task spec", "turn this idea into requirements", "what exactly should we build". Interrogates the person for what they know instead of proposing content for them to approve, using Gherkin's own grammar to decide which questions must be asked and when the document is complete. Emits a .feature behavioural contract plus a spec.json manifest that the task skill consumes.Votes: 0GitHub stars: 2
- Debug IssueUse when a bug report or failing test names a symptom and the code path producing it is not yet known — trace the call chain from symptom to entry point before proposing a fix. Trigger phrases: "why does this fail", "trace this bug", "find where this is called from", "what calls this function", "did a recent change cause this". Not a replacement for the general reproduce-isolate-fix discipline (a `systematic-debugging` skill, if present, governs that overall loop); reach for this skill specif...Votes: 0GitHub stars: 2
- Den RefreshUse when an already-scaffolded project is behind the framework — a drift notice appeared, a new ai-badger version shipped, or the user asks to "refresh"/"update ai-badger". Reports what changed, backs up .ai-badger/, and re-scaffolds from the project's existing config.Votes: 0GitHub stars: 2
- Design Gate AuditUse when auditing a design doc's acceptance gates BEFORE implementation: check every gate would fail if the feature were broken (HONEST) and the named test file/framework/seam exists (FEASIBLE). Attacks vacuous negatives, timing-window vacuity, port races, env poisoning, unprovable real-time halves. Pairs with dotnet-hosted-service-testing for FakeTimeProvider mechanics.Votes: 0GitHub stars: 2
- Design TestsUse when tests have to be designed or written for a target — "write tests for X", "add coverage here", "what should I test", a new behaviour with no test yet, a bug that needs a reproduction test, a coverage gap someone wants closed, or a bare "write some tests" with nothing named. Works with a target given or none given. Not for judging tests that already exist (review-tests) and not for diagnosing one already-flaky failure (dotnet-flaky-test-diagnosis).Votes: 0GitHub stars: 2
- Differential Feature RefactorUse when a feature already exists in code but has drifted from — or was never reconciled with — its intended design, and someone must decide what changes before a refactor is scoped. Triggers: two parallel implementations of the same thing, code that reads as dead but may be a ratified extension point, an architecture nobody can tell from accumulated cruft, or a refactor about to be scoped off review documents instead of decisions.Votes: 0GitHub stars: 2
- Documentation Drift AuditUse when auditing docs for drift vs code ('audit and fix documentation drift'): inventory claims with path:line, verify each against real files (scaffolders, manifests, hooks), classify verifiably-false vs design-position vs ambiguous vs historical, fix only the false, and report A/B/C. Also for post-merge doc-gap audits and user-facing doc compaction rewrites.Votes: 0GitHub stars: 2
- DocumentationUse when a task concerns the project's documentation tree itself — creating it where none exists, updating or amending documents in it, or migrating/reorganising an existing docs layout — and you must pick which specialized documentation skill covers it. This gateway routes; read manifest.json to choose a member and open that member's SKILL.md. Not for writing prose inside a document that already has a home.Votes: 0GitHub stars: 2
- Migrate DocumentationUse when an existing documentation tree must be reorganised wholesale — "migrate the docs", "reorganise docs/", hundreds of files with no structure, overlapping documents that contradict each other, a docs directory nobody can navigate, or documentation whose accuracy is unknown and must be established before anyone relies on it. Also use to resume a migration already in progress. Not for creating a tree that does not exist (use scaffold-documentation) and not for a single documentation chang...Votes: 0GitHub stars: 2
- Scaffold DocumentationUse when a repository has no documentation tree yet, or the canonical docs layout is missing, incomplete or was hand-created — "set up docs", "scaffold documentation", "create the docs structure", a fresh repo with only a README, a docs directory missing its directory READMEs, or a structure check that reports absent directories. Not for adding or editing a document (use update-documentation), and not for reorganising docs that already exist (use migrate-documentation).Votes: 0GitHub stars: 2
- Update DocumentationUse whenever documentation must change to match something that already changed — after a code change, ADR, schema change or PR lands, and when the user says "update the docs", "document this", "add a how-to for X", "the README is wrong", "this doc is stale", or a reviewer reports docs drift. Also use before creating any new document, to decide where it belongs. Triggers include a doc that contradicts the code, a fact nobody can source, and a new page with no obvious home. Not for creating the...Votes: 0GitHub stars: 2
- Dotnet WorkloadUse when working on any .NET workload concern — BDD/Reqnroll testing, immutable domain modeling, flaky test diagnosis, BackgroundService/IHostedService review or testing, [LoggerMessage] log-line design, MCP servers in .NET, SQLCipher-encrypted SQLite, System.CommandLine CLI parsing, .NET tool/NuGet publishing, or an observability/instrumentation review — and you must pick which specialized dotnet skill covers it. This gateway routes; read manifest.json to choose a member and open that member...Votes: 0GitHub stars: 2
- Dotnet Bdd TestingUse when adding Gherkin .feature files / a BDD runner to a .NET project: Reqnroll is the only live option (SpecFlow is EOL — never recommend it), xunit.v3 + CPM integration, tags/@ignore/Skip and Rule: blocks, or un-ignoring dormant scenarios. Includes the build-time code-behind recipe, feature-file overlap policy, and verified package facts.Votes: 0GitHub stars: 2
- Dotnet Domain ModelingUse when modeling immutable C#/.NET domain layers: sealed records with required/init props, CommunityToolkit.Diagnostics guards (and when to hand-roll them), state-transition methods, policy objects, extension-point interfaces (DIM), FluentValidation nested validators, ArchUnitNET purity enforcement — with TDD for pure domain layers. Triggers: DDD aggregates/value objects, domain-purity rules, validator design.Votes: 0GitHub stars: 2
- Dotnet Flaky Test DiagnosisUse when a .NET test fails in the full suite but passes alone (or flakes intermittently): classify via the ladder — intra-test race (lock-guard fake collections), inter-test contention (xunit v3 DisableParallelization collections), or environmental flakes (child PATH/env, cold-worktree asset provisioning) — before blaming the branch. Includes the clean-main baseline check and gate discipline.Votes: 0GitHub stars: 2
- Dotnet Hosted Service ReviewUse when reviewing a PR that adds or modifies a .NET BackgroundService/IHostedService — background extraction loops, watchers, sync, sweep, or any poll loop. Checklist: ExecuteAsync try/catch coverage (StopHost kills the process), cancellation filtering, PeriodicTimer semantics, store-level idempotency vs TOCTOU, settings-channel parsing, LoggerMessage invariants. Produces numbered findings + severity + file:line.Votes: 0GitHub stars: 2
- Dotnet Hosted Service TestingUse when writing or reviewing .NET BackgroundService tests with FakeTimeProvider/TimeProvider: lost-first-Advance semantics, inline-vs-threadpool timer callbacks, poll-loop test honesty (invocation counters, not side-effect counts), tick derivation from timeouts, DI registration smoke tests, vacuous-gate detection. Verified on .NET 10; includes an empirical probe script.Votes: 0GitHub stars: 2
- Dotnet Logger Message DesignUse when designing or testing [LoggerMessage] log lines in .NET: nested static partial Log classes, explicit EventIds with per-category ranges, no call-site interpolation, collection parameters (pre-join at the call site), per-item detail logs vs counts, and FakeLogger-based log assertions (generic vs non-generic compile contract, LatestRecord/AllRecords, RED-first EventId tests).Votes: 0GitHub stars: 2
- Dotnet Mcp ServerUse when adding MCP (Model Context Protocol) tools or servers to a .NET project: tool/prompt registration with [McpServerTool]/[McpServerPrompt], stdio or Streamable-HTTP host wiring (dual-mode, port traps), DI + typed HttpClient for REST-backed tools, unit tests with mock HTTP handlers, tool-inventory tests that assert the REGISTERED surface, and SDK 2.x specifics (McpException error signaling, request filters, tool-name derivation).Votes: 0GitHub stars: 2
- Dotnet Sqlcipher EncryptionUse when working with SQLCipher-encrypted SQLite in .NET (e_sqlite3mc / SQLitePCLRaw bundle): raw 256-bit keys via Password='x'<hex>'', deriving keys from ed25519 SSH keys, PRAGMA rekey constraints (WAL unsupported), pluggable key-source providers (env/keychain/vault) with the pre-open sidecar pattern, and Dapper-over-SQLite3MC mapping traps.Votes: 0GitHub stars: 2
- Dotnet System CommandlineUse when adding CLI argument parsing to a .NET app or dotnet tool: System.CommandLine 2.0.x GA idioms (parse-first, HelpAction/VersionOptionAction detection, Option.Validators, FromAmong), parser-landscape verdicts (Cocona archived — don't adopt), and the stdio-MCP trap where help/version must render to stderr. Includes Cocona-maintenance guidance for existing tools.Votes: 0GitHub stars: 2
- Dotnet Tool PublishingUse when packaging or publishing a .NET CLI tool (PackAsTool) or library to NuGet: the MSB3030 build-before-pack trap (and its Web-SDK inversion), multi-RID matrix shells + the shell-race fix, gitignored bundled assets, Trusted Publishing/OIDC with human approval gates, the 409-published-nothing diagnosis, ToolCommandName/PATH shim rules, and full fresh-install verification for MCP tools with bundled models.Votes: 0GitHub stars: 2
- Observability Contract ReviewUse when reviewing claims that 'all calls are instrumented': span+metrics helper diffs, tool-layer try/catch instrumentation, N/N tool-surface parity tests. Checks path coverage, not call-site presence — filtered-catch escape holes, exactly-once recording, Activity status/tag ordering, instrumentation-test honesty, CI Speed-trait blind spots, metrics-unchanged verification.Votes: 0GitHub stars: 2
- Evidence First ResearchUse when a question needs investigating and the answer will be acted on — "research X", "look into whether Y", "find out how Z works", "is this worth doing", "compare these options", a benchmark someone will quote, or a claim that has to survive being challenged. Produces a dated record where every finding carries how it is known — measured, read, inferred, or unverified — plus a self-contained HTML view. Not for locating code (that is explore-codebase), tracing one symptom (debug-issue), or ...Votes: 0GitHub stars: 2
- Explore CodebaseUse when arriving at an unfamiliar codebase, or an unfamiliar region of a known one, and the question is "what is here and how is it arranged" rather than "where is this specific thing". Trigger phrases: "help me understand this repo", "what does this project do", "where does X live", "walk me through the architecture", "I'm new to this codebase", "what are the main modules". Not for tracing one symptom to its cause — that is `debug-issue`; not for judging a diff — that is `review-changes`. R...Votes: 0GitHub stars: 2
- Feed BadgerUse when something learned in this repo belongs in the ai-badger framework itself — a new skill, persona, invariant, instruction or fix that is project-agnostic — and the user wants to contribute it back. Opens a draft PR against the framework; refuses anything project-specific.Votes: 0GitHub stars: 2
- Get Raw Text SearchUse when the memory-first gate reported a text search and you need the short-lived raw output from its shell grep or rg capture.Votes: 0GitHub stars: 2
- Git WorkUse when a git push fails for a reason the quality gate did not cause, CI goes red on a pushed branch, or a PR moves through review and merge outside the tracked-task flow: non-fast-forward recovery with force-with-lease, CI log triage and flake attribution, draft-to-squash PR lifecycle, squash-merge conventions, and join-time conflict resolution on plain branches.Votes: 0GitHub stars: 2
- HumanizerUse when writing or editing prose (documentation, blog posts, release notes, PR descriptions, emails) to strip AI writing artifacts, apply research-grounded humanization levers, and adopt a natural human voice.Votes: 0GitHub stars: 2
- Maintain Agent InstructionsUse when agent instruction files have drifted from each other or from the policy model — CLAUDE.md, copilot-instructions.md, AGENTS.md, hosted-review and path-scoped instruction files — or when validation/drift checks fail in CI. Reconciles them from the machine-readable model in .ai-badger/agent-instructions/.Votes: 0GitHub stars: 2
- Mcp IndexUse when MCP tool selection needs help — the agent keeps picking the wrong tool, server tool definitions are bloating the prompt, or MCP servers were just added or removed. Manages .ai-badger/mcp-tools.json: tags, intent descriptions, and the hook that recommends tools per turn.Votes: 0GitHub stars: 2
- Multi Agent CommunicationUse when multiple agent sessions share one project and must coordinate without stepping on each other — announcing started work, touched files, opened PRs, review requests, review feedback, and merges to main over the project message bus. Covers when to broadcast, the message shape, and the ack-without-reply rule that keeps the bus loop-free.Votes: 0GitHub stars: 2
- Multi Lane Report AssemblyUse when assembling outputs from 2+ parallel research/review lanes into one evidence-graded record: lift finding blocks verbatim from the authoritative full summaries (never the truncated delegation transcripts), enforce the lane contract (### F# — claim [GRADE], Evidence line), truncate at embedded '## Still open' headers, renumber, and gate the result.Votes: 0GitHub stars: 2
- Owner Gate ReviewUse when a design, refactor or review document needs a per-decision ruling from one human reviewer and the answers must come back attached to the decision they belong to. Triggers: pasting a long document into chat and getting a wall of prose back, an answer that can't be matched to its question, a reviewer hand-editing answer slots in markdown, or a set of decisions that must each be approved, changed, rejected or deferred before work is scoped.Votes: 0GitHub stars: 2
- Pre Push Gate DebuggingUse when a pre-push quality gate blocks git push or a lane fails: read the gate's own logs first (reproduce one lane), run single lanes for fast iteration, test the working tree you intend to push, handle E2E/infra cross-run state contamination, worktree node_modules gotchas, and build a manual repro harness when lane output hides the real error.Votes: 0GitHub stars: 2
- Prompt MarkersUse when a prompt starts with a marker prefix — `h:`/`hint:` (a lead to validate before acting), `f:`/`feedback:` (a correction to apply immediately), `e:`/`extension:` (a request to widen scope), `q:`/`queue:` (a queued task for after current work), `i:`/`important:` (important, high priority) or `i!:`/`important!:` (immediate emergency interrupt) — every marker also accepts a `!` importance token between alias and colon, making it interrupt-grade — or when the user asks to add, change, or i...Votes: 0GitHub stars: 2
- QaUse when the user wants a question-and-answer session against a context — "qa {context}", "I have questions about X", or a question asked against supplied material — or wants the session's questions and grounded answers saved as a summary. If no context is given, ask for it first; every answer carries its grounding, and the session closes with a summary in docs.Votes: 0GitHub stars: 2
- Quick TaskUse when a change is small enough to skip the full task pipeline — one focused fix or small feature that fits a single commit on a branch cut from fresh main and merged via PR with auto-merge: a minimal plan, touched-surface tests only, the project's fast gates (lint, docs), one quick focused review, one commit per PR. Escalate to `task` the moment the change outgrows that shape.Votes: 0GitHub stars: 2
- Refactor SafelyUse when renaming, moving, extracting, or removing code and every affected location must be known before the first edit — a rename that spans call sites, an extraction that changes a signature, or a removal that might delete something still in use. Trigger phrases: "refactor this safely", "rename X everywhere", "is this code still used", "find everything that calls this before I change it", "preview this refactor". Not for reconciling a feature whose implementation has drifted from its intend...Votes: 0GitHub stars: 2