rune

Alias for /rune:cancel-arc --variant=batch. Cancel an active arc batch loop. Removes the state file so the Stop hook allows the session to end after the current arc completes. Delegates to /rune:cancel-arc with --variant=batch for all logic. <example> user: "/rune:cancel-arc-batch" assistant: "Arc batch loop cancelled at iteration 2/4." </example>

Alias for /rune:cancel-arc --variant=hierarchy. Cancel an active arc-hierarchy execution loop. Marks the state file as cancelled so the next child arc invocation does not proceed. The currently-executing child arc (if any) will finish normally. Delegates to /rune:cancel-arc with --variant=hierarchy for all logic. <example> user: "/rune:cancel-arc-hierarchy" assistant: "Arc hierarchy loop cancelled. Currently executing child [03] will finish normally." </example>

Alias for /rune:cancel-arc --variant=issues. Cancel an active arc-issues batch loop. Removes the state file so the Stop hook allows the session to end after the current arc completes. Delegates to /rune:cancel-arc with --variant=issues for all logic. <example> user: "/rune:cancel-arc-issues" assistant: "Arc issues loop cancelled at iteration 2/4." </example>

Cancel an active arc pipeline and gracefully shutdown all phase teammates. Completed phase artifacts are preserved. Only the currently-active phase is cancelled. Also cancels arc-batch, arc-hierarchy, and arc-issues loop state files owned by this session. Use --status to inspect arc pipeline health without cancelling (runs rune-status.sh). Use --list-active to list all active arc-related state files without cancelling anything. Use --variant=batch|hierarchy|issues to cancel only a specific loop type (thin alias support). <example> user: "/rune:cancel-arc" assistant: "The Tarnished halts the arc..." </example> <example> user: "/rune:cancel-arc --status" assistant: "Displays arc pipeline status report without cancelling." </example> <example> user: "/rune:cancel-arc --list-active" assistant: "Lists all active arc-related state files owned by this session." </example>

Cancel an active Roundtable Circle audit and gracefully shutdown all Ash teammates. Partial results remain in tmp/audit/ for manual inspection. <example> user: "/rune:cancel-audit" assistant: "The Tarnished dismisses the audit Circle..." </example>

Traces API contract changes across the full request/response lifecycle: route definitions, controller handlers, request validators, response serializers, API docs, and client SDK references. Detects breaking changes in public interfaces.

Hunts for security breaches — threat modeling, auth boundary gaps, data exposure vectors, CVE patterns, and input sanitization depth. Goes deeper than checklist-level security review.

Traces business logic impact across service methods, domain rules, validators, and state machines. Identifies ripple effects when core business rules change.

Traces configuration and dependency impact across environment variables, config files, deployment manifests, CI/CD pipelines, and feature flags. Detects deployment-time breakage from config drift.

Traces impact of data layer changes across the full persistence stack: schema definitions, ORM models, serializers, migrations, and seed data. Identifies ripple effects when data models change.

Browser automation knowledge using Vercel's agent-browser CLI. Teaches Claude how to use agent-browser for E2E testing, screenshot capture, and UI verification. Trigger keywords: agent-browser, browser automation, E2E, screenshot, navigation, frontend test, browser test, UI verification.

Multi-agent code review using Agent Teams. Summons up to 8 built-in Ashes (plus custom Ash from talisman.yml), each with their own dedicated context window. Handles scope selection, team creation, review orchestration, aggregation, verification, and cleanup. Optional `--deep` runs multi-wave deep review with up to 18 Ashes across 3 waves. Phase 1.5 adds UX reviewers when `talisman.ux.enabled` + frontend files detected. Phase 1.6 adds design fidelity reviewer (DES prefix) when `talisman.design_review.enabled` + frontend files detected. Phase 1.7 adds data flow integrity reviewer (FLOW prefix) when 2+ stack layers detected in diff. <example> user: "/rune:appraise" assistant: "The Tarnished convenes the Roundtable Circle for review..." </example>

Use when implementing multiple plan files overnight or in batch, when a previous batch crashed mid-run and --resume is needed, when tracking progress across multiple sequential arc runs, or when using a queue file (one plan path per line) instead of a glob. Use when crash recovery is needed for interrupted batch runs. Covers: Stop hook pattern, progress tracking via .rune/arc-batch-loop.local.md, --dry-run preview, --no-merge. Keywords: arc-batch, batch, queue file, overnight, --resume, crash recovery, progress tracking, sequential plans. <example> Context: User has multiple plans to implement user: "/rune:arc-batch plans/*.md" assistant: "The Tarnished begins the batch arc pipeline..." </example> <example> Context: User has a queue file user: "/rune:arc-batch batch-queue.txt" assistant: "Reading plan queue from batch-queue.txt..." </example>

Hierarchical plan execution — orchestrates parent/child plan decomposition with dependency DAGs, requires/provides contracts, and feature branch strategy. Use when a plan has been decomposed into child plans via /rune:devise Phase 2.5 (Hierarchical option) and frontmatter shows `hierarchical: true` with a `children_dir`. Handles: topological sequencing, contract verification, partial failure recovery, and per-child feature branch management. Keywords: hierarchical, parent plan, child plan, decomposition, DAG, dependency, shatter, children_dir, requires, provides, contract matrix, arc-hierarchy. <example> Context: User has a parent plan with child plans decomposed user: "/rune:arc-hierarchy plans/2026-02-23-feature-auth-plan.md" assistant: "The Tarnished reads the execution table and begins executing child plans in topological order..." </example> <example> Context: User wants to resume after a child plan failure user: "/rune:arc-hierarchy plans/parent.md --resume" assistant: "Resuming hierarchy execution. Found 2/5 children completed. Next executable: 03-permissions..." </example>

Use when processing GitHub Issues as the arc work queue — fetching issue details, auto-generating plans, running /rune:arc for each, then posting results back to the originating issues. Covers: label-driven batch (--label), file-based queue, inline issue numbers, resume mode (--resume), paging (--all), dry-run preview, cleanup of orphaned labels (--cleanup-labels). Use instead of arc-batch when your work queue lives in GitHub Issues, not plan files. Closes the loop: Issue → Plan → Arc → PR → Comment → Close (via Fixes #N). Keywords: arc-issues, github issues, issue queue, issue backlog, batch from issues, label-driven, rune:ready, --label, --all, --resume, --cleanup-labels, issue-to-plan. <example> Context: User has GitHub issues labeled "rune:ready" to implement user: "/rune:arc-issues --label \"rune:ready\"" assistant: "Fetching issues with label rune:ready..." </example> <example> Context: User has a file with issue numbers user: "/rune:arc-issues issues-queue.txt" assistant: "Reading issue queue from issues-queue.txt..." </example> <example> Context: User wants to process specific issues user: "/rune:arc-issues 42 55 78" assistant: "Processing issues #42, #55, #78..." </example>

64 hooks across 17 events