auriga-go

Orchestrate the auriga-go workflow by reading state and advancing CLAUDE.md phases.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Ben2pc/auriga-cli --skill auriga-go
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auriga-go
Source: https://github.com/Ben2pc/auriga-cli/tree/main/plugins/auriga-go/skills/auriga-go
Command: npx skills add https://github.com/Ben2pc/auriga-cli --skill auriga-go

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the navigation and progression of the auriga-go workflow by reading the current state and advancing CLAUDE.md through its phases, reducing manual tracking and human prompts.

Core Features & Use Cases

  • Orchestrates the auriga-go workflow by determining the next required phase and pushing the action to the appropriate sub-skills.
  • Supports explicit invocation via /auriga-go or natural-language prompts referencing the workflow, including modes step, auto, and ship with an optional max-iter.
  • Provides autotracking, context re-reading, and readiness checks to ensure auditable progression toward PR readiness in ship mode.
  • Lets users resume after /clear and handle drift scenarios (e.g., divergent branch state or draft PRs).

Quick Start

Invoke the /auriga-go trigger to drive the workflow forward and optionally specify a mode like step, auto, or ship.

Frequently Asked Questions about auriga-go

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

FAQPage Schema
How do I automate workflow progression through CLAUDE.md phases?

You can automate CLAUDE.md workflow progression by invoking the auriga-go trigger, which reads the current state and pushes the next action to the appropriate sub-skills. This reduces manual tracking and human prompts.

What is the difference between step, auto, and ship modes in workflow orchestration?

Workflow orchestration modes control progression depth: step advances one phase at a time, auto continues automatically, and ship enforces a readiness contract for PR readiness. You can also limit auto iterations using the max-iter option.

How do I resume an automated workflow after clearing context or encountering branch drift?

To resume an automated workflow after context clearance or branch drift, the orchestrator re-reads the workflow context and current state. It then reconciles divergent branch states or draft PRs to ensure auditable progression.

Can I enforce readiness checks before finalizing a pull request in ship mode?

Yes, ship mode enforces a strict readiness contract before finalizing a pull request. The orchestrator performs readiness checks, records steps for auditability, and recommends actions until the PR is fully ready.

Do I need to manually track workflow state when using natural-language prompts?

No, you do not need to manually track workflow state when using natural-language prompts. The orchestrator provides autotracking by reading the current state and determining the next required phase automatically.