speckit-guards

Spec Kit workflow safety checks validate implementation, commit, and pull request conditions before allowing protected actions to proceed. This blocks auto-commits until tests pass, secrets are absent, and repository conditions are acceptable.

Pre-action guards for Codex automation validate safety conditions, token observability, and read-only boundaries before protected actions proceed. They are needed when automating implementation, commits, PR creation, and agent definition validation phases.

Yes, you need bash, git, and jq installed to run Spec Kit validation scripts. These dependencies are required for script execution, repository automation, and JSON validation of agent definitions and token observability artifacts.

Token observability in repository workflows records token steps and generates per-run reports, summaries, and quality notes for workflow tracking. It confirms token-analyzer availability and ensures read-only boundary protection for approved paths.

Validate Codex agent definition toml files by checking `.codex/agents/*.toml` files for required fields, structure, and phase alignment. Guard scripts verify these definitions conform to expected workflow requirements before protected actions proceed.

If validation fails during a Spec Kit guard phase, the protected action is blocked from proceeding. The guardrails prevent commits or PR creation until tests pass, secrets are absent, and all repository conditions are acceptable.