All authors
Claude Skills by ChrisRoyse
github.com/ChrisRoyse11 skills0 installs1 views
- Astro FanoutParallel issue-completion playbook for ASTROLABE — fan out worktree-isolated subagents one per pure-Rust crate, keep astrolabe-server and cross-crate work sequential, consolidate server-pending branches into one native gate run, octopus-merge disjoint branches, orchestrator owns all GitHub state. Use when parallelizing work across multiple ready issues or crates, orchestrating subagent waves, or merging a completed wave. Not for single-issue work (astro-issue).Votes: 0GitHub stars: 4
- Astro FsvManual Full State Verification doctrine for ASTROLABE — identify the source of truth, exercise the real artifact yourself, then independently read back the persisted bytes (SQLite artifact, vault, ledger, files), run the edge-case triad, use the smallest sufficient dataset, and format evidence for issue comments. Use when verifying any change/tool result, deciding whether something "worked", or preparing closing evidence. Tests, return values, API echoes, green checkmarks, and log lines are n...Votes: 0GitHub stars: 4
- Astro HandoffHonest pause/stop/handoff for ASTROLABE sessions — verifies hygiene (target/ absent, no stray worktrees/branches/locks), records exactly what is done (verified vs unverified), what is not, the next concrete step, and any uncommitted local state on the active GitHub issue, then swaps status labels. Use before any pause, stop, or turn end with unfinished issue work, when context compaction is imminent, or when abandoning a claim. GitHub issues are the only handoff medium — never local SITREP/tm...Votes: 0GitHub stars: 4
- Astro IssueDrives one ASTROLABE GitHub issue through the mandatory lifecycle — pick, claim, verify prior progress, scoped work, FSV proof, evidence, close. Use when starting, resuming, or closing work on a GitHub issue, choosing the next issue, checking a DoD box, or swapping status labels. Not for filing new issues (use astro-new-issue) or pausing mid-issue (use astro-handoff).Votes: 0GitHub stars: 4
- Astro New IssueFiles a well-formed ASTROLABE GitHub issue for a discovered problem — correct labels (area/status/sev/type), milestone mapping, Blocked-by/Blocks links, Scope + DoD skeleton with FSV requirements — and links it from the active issue with a telemetry block. Use whenever work reveals a problem, coverage gap, or adjacent improvement outside the current issue's scope. Never expand scope in place; never carry a problem forward silently.Votes: 0GitHub stars: 4
- Astro ResumeResume protocol for ASTROLABE sessions — injects live git/lock/toolchain/issue state, then walks the mandatory re-reads (AGENTS.md, CLAUDE.md, active issue and all its comments) before any action. Use at the start of a fresh session on existing work, after context compaction, or when picking up another session's in-progress issue. Prevents redoing verified DoD items and acting on stale lock/toolchain assumptions.Votes: 0GitHub stars: 4
- Astro Skill LintValidates ASTROLABE project skills fail-closed — frontmatter parses, name matches directory, description within budget (≤1024 chars, ≤1536 combined with when_to_use), body ≤500 lines, referenced files exist, no unknown frontmatter keys, no command/skill name collisions. Use after creating or editing anything under .claude/skills or .claude/commands, and before committing skill changes.Votes: 0GitHub stars: 4
- Astro TelemetryMachine-readable agent telemetry for ASTROLABE — the astro-telemetry/v1 JSON block format posted in GitHub issue comments, and gh/jq recipes to reconstruct project state (done, in flight, blocked, gate history, handoffs) from the tracker. Use when posting claim/evidence/gate/close/handoff/filed comments, auditing what previous sessions did, or answering "what is the current project state / what happened on issue N".Votes: 0GitHub stars: 4
- Astro Vendor PatchRETIRED (#286). The vendoring doctrine is dissolved — calyx/ and cbm/ are owned first-class source, edited in place. There is no pin, no patch applier, and no hash-checked overlay. Use when tempted to reach for pins/overlays/verify-pins for a CBM or Calyx change.Votes: 0GitHub stars: 4
- PushrepoCommits and pushes all repository changes with ASTROLABE discipline — issue-referenced commit body, hygiene sweep (no target/, .tmp, scratch, logs, or test databases staged), secret-scanner awareness, and pushed-state readback. Replaces the former pushrepo command, which invoked a validation hook that does not exist in this repository.Votes: 0GitHub stars: 4
- SitrepHonest situation report for the current ASTROLABE session — raw assessment of git state, work in flight, green/red flags, and project health, recorded on the active GitHub issue (issues are the only durable state; no ./tmp SITREP files) and summarized inline. Use when asked for a sitrep/status/honest assessment, or before risky transitions. For a plain pause/stop record, astro-handoff alone suffices.Votes: 0GitHub stars: 4