Menu
Regenerate docs/schemas/config.schema.json from the Config struct. Use after editing internal/config/config.go.
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.
Run agnostic-ai sync --check, interpret the diff, and pick the right next step. Use after editing specs or adapters.
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 | regen-schema |
| description | Regenerate docs/schemas/config.schema.json from the Config struct. Use after editing internal/config/config.go. |
The JSON Schema published at docs/schemas/config.schema.json is reflected from the config.Config Go struct.
Any of:
config.Config, config.Output, config.Sources, or config.Gitignore.yaml: or json:) on those types.version.go run ./cmd/schemagen from the repo root.git diff docs/schemas/config.schema.json to confirm the change is what you intended.Schema drift job fails if they land separately.Never hand-edit the schema file. The next regen overwrites it.