All authors
Claude Skills by arbiterForge
github.com/arbiterForge162 skills0 installs274 views
- Ca ChoreSanctioned lane for non-behavioral work — docs-only edits, dependency bumps, reverts. Type-scaled gates; no TDD demanded of prose.Votes: 0GitHub stars: 147
- Ca CleanupClean up an already-merged local branch after proving containment. Confirm each discard and preserve unique work.Votes: 0GitHub stars: 147
- Ca CommandsShow the codeArbiter command catalog — the public command list and what each routes to.Votes: 0GitHub stars: 147
- Ca CommitCreate a verified local Git commit when committing changes is requested. Not for explaining commit history, drafting a message only, or postponing a commit. Applies every commit gate and never implies a push or PR.Votes: 0GitHub stars: 147
- Ca ConflictStop everything and surface a rule conflict — persona vs. docs vs. code. Present both sides and the conflict-hierarchy level; the user resolves. No silent reconciliation.Votes: 0GitHub stars: 147
- Ca Context CheckAudit stale provenance-tracked docs on request. Report first; re-scout or re-baseline only for selected docs.Votes: 0GitHub stars: 147
- Ca Create ContextBuild project context from an existing codebase through isolated scouts, resolve gaps, and preserve initialization gates.Votes: 0GitHub stars: 147
- Ca DebugInvestigate an unexplained defect or unexpected behavior without changing application code. Use for root-cause diagnosis and an evidence-backed handoff, including a bounded unresolved result. Not for implementing a known fix, new features, or explanation-only questions.Votes: 0GitHub stars: 147
- Ca DecomposeDevelop greenfield project context through a layered interview, preserve decisions, and initialize only after the required gates.Votes: 0GitHub stars: 147
- Ca DoctorVerify the active host install, package, command ownership, enforcement, and harmless live-fire probe. Read-only.Votes: 0GitHub stars: 147
- Ca FeatureStart a feature: brainstorm a spec, get it approved, then drive it test-first through the pipeline. The one entry to implementation.Votes: 0GitHub stars: 147
- Ca FixFix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates.Votes: 0GitHub stars: 147
- Ca InitOpt this repo into codeArbiter — scaffold the root-level .codearbiter/ state store.Votes: 0GitHub stars: 147
- Ca MetricsRead-only 3-metric governance glance — override rate, small-lane rate, sprint low-confidence ratio — each with a trend arrow vs. the prior 20-commit window.Votes: 0GitHub stars: 147
- Ca OverrideSanctioned, logged bypass of a gate or hard rule — one audit line, then proceed.Votes: 0GitHub stars: 147
- Ca PrOpen a PR or finish branch disposition; route CI watching and post-merge cleanup to their owners. Merge and discard need explicit authority.Votes: 0GitHub stars: 147
- Ca PreviewZero-onboarding, read-only dry-run of the reviewer fleet against the current uncommitted diff. Predicts reviewers, runs the state-free secret scan, writes nothing.Votes: 0GitHub stars: 147
- Ca ReconcileInspect architectural variances with SMARTS; record only explicit user choices. Report-only requests make no changes.Votes: 0GitHub stars: 147
- Ca RefactorRestructure code without changing observable behavior: rename, extract, inline, move, deduplicate, or replace an internal implementation with an equivalent one. Prove parity through unchanged pre-existing tests. Not for new behavior, bug fixes, explanation-only questions, or committing finished work.Votes: 0GitHub stars: 147
- Ca ReleasePrepare a declared release target, or preview it with --dry-run. Derive its version and require authorization before publication.Votes: 0GitHub stars: 147
- Ca ReviewReview a diff with the reviewer fleet, funneled to one triaged verdict. Targets the current working diff, a path, or an inbound GitHub PR.Votes: 0GitHub stars: 147
- Ca SpikeExploratory spike on a throwaway branch — answer a named question with disposable code. Never merges; exits to a findings note or $ca-feature.Votes: 0GitHub stars: 147
- Ca SprintAutonomous sprint — one interactive spec gate, then plan-to-PR execution with every auto-decision SMARTS-scored and logged. Hard gates remain true stops.Votes: 0GitHub stars: 147
- Ca StandupDaily repo hygiene — review the day's repo state, then perform the cleanups under per-action confirmation. Fast-forward only, never destructive without a yes.Votes: 0GitHub stars: 147
- Ca StatusShow the project's current state at a glance — stage, open tasks, open questions, overrides since the last checkpoint, current branch. Read-only.Votes: 0GitHub stars: 147
- Ca TaskThe sanctioned task-board mutator — add a queued task, start one (flips to in-progress and stamps the date, minting a dotted ID on pick-up), or mark an in-progress task done. The only blessed write to open-tasks.md.Votes: 0GitHub stars: 147
- Ca Threat ModelThreat-model a sensitive design with STRIDE on request. Read-only analysis of threats, controls, and implementation constraints.Votes: 0GitHub stars: 147
- Ca TribunalRun an opt-in deep codebase audit with persisted findings. Confirm cost before dispatch; filing and telemetry need separate approval.Votes: 0GitHub stars: 147
- Ca WatchWatch a PR's CI to completion — diagnose on red, notify and offer the merge on green. Never auto-merges.Votes: 0GitHub stars: 147
- BrainstormingThe Socratic spec-refinement front of /feature, and the planning front of /sprint. Routed to BEFORE any code — it turns a one-line idea into a concrete spec with testable criteria, ready for initial combined sprint review or explicit sequential approval. Five gated phases — frame, shape, refine, write, review-and-approve. No implementation before an approved spec; the caller retains required planning, execution and delivery ordering. Each acceptance criterion becomes one tdd Phase 1 obligation.Votes: 0GitHub stars: 147
- Commit GateCreate a verified local Git commit when committing changes is requested. Not for explaining commit history, drafting a message only, or postponing a commit. Applies every commit gate and never implies a push or PR.Votes: 0GitHub stars: 147
- Context CheckAudit stale provenance-tracked docs on request. Report first; re-scout or re-baseline only for selected docs.Votes: 0GitHub stars: 147
- Context CreationBuild project context from an existing codebase through isolated scouts, resolve gaps, and preserve initialization gates.Votes: 0GitHub stars: 147
- Crypto ComplianceThe banned-primitive gate. Routed to when changed code hashes, signs, encrypts, derives keys, generates security-relevant randomness, configures TLS, or imports a crypto library. Rejects broken primitives, disabled TLS verification, and home-rolled crypto; the approved-primitive list lives in security-controls.md. The auth-crypto-reviewer agent is dispatched as the reviewer.Votes: 0GitHub stars: 147
- Decision LifecycleRecord user-decided ADRs or inspect their health read-only. Preserve attribution and acceptance evidence.Votes: 0GitHub stars: 147
- Decision VarianceInspect architectural variances with SMARTS; record only explicit user choices. Report-only requests make no changes.Votes: 0GitHub stars: 147
- DecomposeDevelop greenfield project context through a layered interview, preserve decisions, and initialize only after the required gates.Votes: 0GitHub stars: 147
- Dispatching Parallel AgentsThe parallel fan-out primitive. Routed to by any skill or command that splits work across independent units and dispatches an agent per unit — subagent-driven-development, /sprint, parallel /review. It owns the dispatch/collect/funnel discipline: bound concurrency, isolate units, collect every result, dedupe overlap, and funnel through finding-triage then the read-only verdict-aggregator. Raw agent output is never consumed before the funnel runs; an agent that errors records its unit as incom...Votes: 0GitHub stars: 147
- Executing PlansThe checkpoint coordinator for /feature. Routed to by /feature once a writing-plans plan exists. Uses authored HTML checkpoints or bounded legacy batches, delegates each scope to subagent-driven-development (fresh author agent per task, full review chain, fresh verification), then stops for a human checkpoint before the next batch. The checkpointed counterpart to /sprint's autonomous run.Votes: 0GitHub stars: 147
- Finishing A Development BranchOpen a PR or finish branch disposition; route CI watching and post-merge cleanup to their owners. Merge and discard need explicit authority.Votes: 0GitHub stars: 147
- Post Merge CleanupClean up an already-merged local branch after proving containment. Confirm each discard and preserve unique work.Votes: 0GitHub stars: 147
- RefactorRestructure code without changing observable behavior: rename, extract, inline, move, deduplicate, or replace an internal implementation with an equivalent one. Prove parity through unchanged pre-existing tests. Not for new behavior, bug fixes, explanation-only questions, or committing finished work.Votes: 0GitHub stars: 147
- 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