astroray-workflows

Routes Astroray development tasks to canonical workflow definitions in .claude/skills.

Updated Dec 27, 2025
One-click install
npx skills add https://github.com/HendrikGC02/Astroray --skill astroray-workflows-hendrikgc02
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: astroray-workflows
Source: https://github.com/HendrikGC02/Astroray/tree/main/.agents/skills/astroray-workflows
Command: npx skills add https://github.com/HendrikGC02/Astroray --skill astroray-workflows-hendrikgc02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working on the Astroray renderer from Codex, developers risk duplicating or drifting from the canonical workflow instructions that live in .claude/skills/. This Skill acts as a bridge, pointing each task to the authoritative workflow definition instead of forking its policy. ## Core Features & Use Cases - Workflow routing table: Maps goals like shipping a package, delegating to opencode, running lint/rebuild/verify, visual checks, and reporting to the correct canonical SKILL.md under .claude/skills/. - Anti-duplication policy: Instructs the agent to read the canonical workflow in full before acting and never fork its policy. - Model resolution guardrail: Ensures opencode delegation resolves models from tier policy at runtime rather than hard-coding model names. - Use Case: You want to ship a new Astroray package from Codex; the Skill directs you to read .claude/skills/pkg-ship/SKILL.md and follow it verbatim. ## Quick Start Ask the agent to route your Astroray task, for example to ship a package or run the lint workflow, using the astroray-workflows bridge.

Frequently Asked Questions about astroray-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Astroray workflows from Codex?▼

Use the astroray-workflows bridge to find the canonical workflow for your goal, then read that workflow's SKILL.md under .claude/skills/ in full before acting. The bridge maps goals like pkg-ship, delegate, lint, and verify to their definitions.

How do I delegate Astroray work to opencode?▼

Follow the delegate workflow referenced by the bridge at .claude/skills/delegate/SKILL.md. The wrapper resolves opencode models from its tier policy at runtime, so never hard-code a model name in a prompt or hook.

Should I copy workflow instructions into Codex prompts?▼

No. The bridge explicitly forbids forking canonical policy; the detailed definitions in .claude/skills/ remain the single source of truth. Always read the relevant SKILL.md in full instead of duplicating it.

What if I am unsure which Astroray workflow owns a task?▼

Use the astroray-index skill first when ownership or an existing script is unclear. It helps locate the right workflow or script before you route through the bridge.

Which workflows does the Astroray bridge cover?▼

It covers dispatch-next, roadmap-orchestrator, pkg-ship, delegate, lint, rebuild-pyd, verify, visual-check, cite-algorithm, architect, strategy-review, run-report, close-round, and file-followup, each living at .claude/skills/<name>/SKILL.md.