Menu
Run agnostic-ai sync --check, interpret the diff, and pick the right next step. Use after editing specs or adapters.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Cut a new agnostic-ai release end to end. Use when the user wants to ship a new version (tag + GitHub Release).
Fetch a GitHub issue, create a branch, implement with TDD, and open a PR
Walk over all open GitHub issues that are unassigned or assigned to the current user, and process each one via the gh-issue skill, sequentially.
Rebuild and serve the WASM playground at docs/playground/. Use after editing the playground source or any code reachable from cmd/agnostic-ai-wasm.
Regenerate docs/schemas/config.schema.json from the Config struct. Use after editing internal/config/config.go.
Author a new agnostic-ai spec (agent, skill, rule, or hook). Use when the user wants to add a new prompt, convention, or hook to their project.
| name | run-sync-check |
| description | Run agnostic-ai sync --check, interpret the diff, and pick the right next step. Use after editing specs or adapters. |
Verifies that emitted target files match what the current specs would produce.
make build../agnostic-ai sync --check. Exit 0 means the working tree matches the bundle.agnostic-ai sync to refresh.agnostic-ai sync and review the diff in git diff.agnostic-ai sync and inspect.sync --check is the gate. A drift exits 1 and fails the workflow. The fix is always to re-sync locally and commit, never to edit the emitted file.