← ClaudeAtlas

setup-verbslisted

Configure or repair a repository's Verbs issue-tracker setting. Use when setting up Verbs in a repo, when a tracker-dependent workflow cannot find its tracker, or when the existing `## verbs` block and Git remote may disagree.
panda850819/verbs · ★ 5 · AI & Automation · score 77
Install: claude install-skill panda850819/verbs
# Setup Verbs Configure the existing per-repository `## verbs` block for tracker-dependent Verbs workflows. This initial contract supports GitHub only. Preview one idempotent edit, ask once, and write only after approval. ## 1. Inspect Read the Git remotes and any root `AGENTS.md` and `CLAUDE.md`. Select the configuration surface with these rules: 1. If exactly one document contains `## verbs`, update that document. 2. If only one document exists, use it and add the block if needed. 3. If both documents contain a block, stop and ask which is canonical, even when their current blocks match. 4. If both documents exist without a block, stop and ask which is canonical. 5. If neither document exists, stop and ask which one to create. Determine the tracker from current evidence: - An existing tracker other than `github`: surface the conflict and stop. Do not overwrite it. - Exactly one GitHub repository identity across the remotes: propose `tracker: github`. - No GitHub remote, or conflicting GitHub repository identities: state the ambiguity and stop. Do not guess or silently configure another tracker. Derive repository identity from the Git remote whenever a later workflow needs it. Never copy owner or repository fields into the config block. ## 2. Preview and gate Show the target file and exact proposed diff. Preserve every existing key and all surrounding content. Add or replace exactly one line: ```yaml tracker: github ``` Ask once: `[approve / reject / skip