62 件（arbiterForge のリポジトリ） ・ 人気順
概要と使いどころ
Create 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.
日本語の概要は準備中です。原文の説明を表示しています。
Stop 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.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate 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.
日本語の概要は準備中です。原文の説明を表示しています。
Develop greenfield project context through a layered interview, preserve decisions, and initialize only after the required gates.
日本語の概要は準備中です。原文の説明を表示しています。
Verify the active host install, package, command ownership, enforcement, and harmless live-fire probe. Read-only.
日本語の概要は準備中です。原文の説明を表示しています。
Start a feature: brainstorm a spec, get it approved, then drive it test-first through the pipeline. The one entry to implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Opt this repo into codeArbiter — scaffold the root-level .codearbiter/ state store.
日本語の概要は準備中です。原文の説明を表示しています。
Read-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.
日本語の概要は準備中です。原文の説明を表示しています。
Sanctioned, logged bypass of a gate or hard rule — one audit line, then proceed.
日本語の概要は準備中です。原文の説明を表示しています。
Zero-onboarding, read-only dry-run of the reviewer fleet against the current uncommitted diff. Predicts reviewers, runs the state-free secret scan, writes nothing.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect architectural variances with SMARTS; record only explicit user choices. Report-only requests make no changes.
日本語の概要は準備中です。原文の説明を表示しています。
Restructure 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.
日本語の概要は準備中です。原文の説明を表示しています。
Exploratory spike on a throwaway branch — answer a named question with disposable code. Never merges; exits to a findings note or $ca-feature.
日本語の概要は準備中です。原文の説明を表示しています。
The 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.
日本語の概要は準備中です。原文の説明を表示しています。
Build project context from an existing codebase through isolated scouts, resolve gaps, and preserve initialization gates.
日本語の概要は準備中です。原文の説明を表示しています。
The 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.
日本語の概要は準備中です。原文の説明を表示しています。
Record user-decided ADRs or inspect their health read-only. Preserve attribution and acceptance evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect architectural variances with SMARTS; record only explicit user choices. Report-only requests make no changes.
日本語の概要は準備中です。原文の説明を表示しています。
Develop greenfield project context through a layered interview, preserve decisions, and initialize only after the required gates.
日本語の概要は準備中です。原文の説明を表示しています。
The 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 incomplete without corrupting the batch.
日本語の概要は準備中です。原文の説明を表示しています。
Open a PR or finish branch disposition; route CI watching and post-merge cleanup to their owners. Merge and discard need explicit authority.
日本語の概要は準備中です。原文の説明を表示しています。
Restructure 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.
日本語の概要は準備中です。原文の説明を表示しています。
Audit stale provenance-tracked docs on request. Report first; re-scout or re-baseline only for selected docs.
日本語の概要は準備中です。原文の説明を表示しています。
OPTIONAL 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.
日本語の概要は準備中です。原文の説明を表示しています。