apastra-setup-ci
Apastra CI Setup
Upgrade your local-first PromptOps workflow with GitHub Actions. This adds PR gating, release automation, and autonomous promotion tracking to your repository.
Apastra is designed to be CI optional. You can start local-first (using your IDE agent as the harness) and upgrade to CI any time just by dropping these workflows into your repository. The core file-based protocol never changes.
When to Use
Use this skill when you want to:
- Enforce that pull requests pass prompt evaluations before merging
- Block PRs that cause prompt regressions against known baselines
- Automate immutable releases of approved prompt packages
- Track promotions of prompts to production environments
How to Set Up CI
When the user asks to "set up apastra CI" or "upgrade to CI", do the following:
Step 1: Copy Workflow Templates
More from bintzgavin/apastra
apastra
PromptOps skills for versioning, evaluating, and shipping AI prompts as disciplined software assets. Agent-as-harness — your IDE agent runs evals, compares baselines, and gates quality.
10apastra-validate
Validate all promptops files against JSON schemas. Catch formatting errors before running evaluations.
5apastra-scaffold
Generate new prompt specs, datasets, evaluators, and suites from templates. Creates correctly-formatted files that pass schema validation.
5apastra-baseline
Establish and manage evaluation baselines for regression detection. A baseline is a known-good scorecard that future runs are compared against.
5apastra-eval
Run prompt evaluations using your IDE agent as the harness. Load suites, execute test cases, score results, and compare against baselines.
5apastra-getting-started
Quick setup guide for apastra PromptOps. Create your first prompt spec, dataset, evaluator, and suite in 5 minutes.
5