All authors
Claude Skills by arbiterForge
github.com/arbiterForge162 skills0 installs274 views
- ReleasePrepare a declared release target, or preview it with --dry-run. Derive its version and require authorization before publication.Votes: 0GitHub stars: 147
- Secret HandlingThe secret-source gate. Routed to when changed code reads, writes, or passes a secret — API key, token, password, connection string, signing key, certificate, or any value that grants access. Validates that every secret comes from the approved store and never lands in source, log, test fixture, error response, image, or LLM prompt. The auth-crypto-reviewer agent is dispatched as the reviewer.Votes: 0GitHub stars: 147
- Security ArchitectureThreat-model a sensitive design with STRIDE on request. Read-only analysis of threats, controls, and implementation constraints.Votes: 0GitHub stars: 147
- Subagent Driven DevelopmentThe implementation engine. Routed to by /sprint (full plan, autonomous) and by executing-plans (scoped batch, checkpoint-gated). One fresh subagent per task — test-first via tdd — followed by spec-compliance review, quality review, and fresh-run verification. No single context accumulates drift, and nothing is accepted on a subagent's word.Votes: 0GitHub stars: 147
- TddThe test-first gate. Routed to by /feature (after the spec is approved), /fix, and /refactor before any implementation code is written. Six gated phases — obligation scan, red, green, obligation verify, coverage, lint. No feature code exists before Phase 1 clears; nothing reaches commit-gate until all six are green.Votes: 0GitHub stars: 147
- TribunalRun an opt-in deep codebase audit with persisted findings. Confirm cost before dispatch; filing and telemetry need separate approval.Votes: 0GitHub stars: 147
- Using Git WorktreesOPTIONAL per-task isolation for autonomous parallel work. Routed to only on explicit opt-in by subagent-driven-development or dispatching-parallel-agents, so parallel units mutate files without colliding. Stands up one worktree per unit, works it in isolation, then integrates each unit back onto the caller's working branch for the caller's single commit-gate + finishing-a-development-branch exit. Never on the default path; it does not bypass a gate or finish per unit.Votes: 0GitHub stars: 147
- Writing PlansThe spec-to-plan bridge. /feature supplies an approved spec; initial full-lane HTML sprint review may supply a ready draft only through draft_for_pair. Creates the same-format plan with exact paths, tests, dependencies and complete criterion coverage. The initial paired review has no execution authority until one real user reply approves both artifacts. Ordinary sequential planning retains approved-source binding and plan approval.Votes: 0GitHub stars: 147
- DebugA fixture skill named debug, colliding with the debug command/agent.Votes: 0GitHub stars: 147
- Dupskill AFirst of two same-named skills, used to prove within-collection dedup still works.Votes: 0GitHub stars: 147
- Dupskill BSecond of two same-named skills, used to prove within-collection dedup still works.Votes: 0GitHub stars: 147
- MyskillA sample skill for fixtures — does one gated thing well.Votes: 0GitHub stars: 147