GeoIntel release gates / Compile, test, contracts and builds (push) Successful in 1m49s
GeoIntel release gates / Python and npm vulnerability policy (push) Successful in 21s
GeoIntel release gates / Production AI image, SBOM and container scan (push) Successful in 5m39s
GeoIntel release gates / Deploy exact gated revision to Unraid (push) Failing after 58m43s
55 lines
1.1 KiB
Markdown
55 lines
1.1 KiB
Markdown
# Skill: Codex Pass Review
|
|
|
|
Use this skill at the end of every pass before returning the result.
|
|
|
|
## Read first
|
|
|
|
- `docs/30-codex-optimization/CODEX_RUN_CHECKLIST.md`
|
|
- `docs/qaqc/CODEX_SELF_REVIEW.md`
|
|
- `docs/qaqc/QUALITY_GATES.md`
|
|
- active pass prompt
|
|
|
|
## Review checklist
|
|
|
|
- [ ] Did the pass stay within scope?
|
|
- [ ] Were governance/invariants respected?
|
|
- [ ] Were API/database contracts preserved or updated intentionally?
|
|
- [ ] Were tests or smoke checks run?
|
|
- [ ] Were docs/status/changelog updated?
|
|
- [ ] Are limitations explicit?
|
|
- [ ] Are next steps clear?
|
|
- [ ] Is there any hidden mock/placeholder behavior?
|
|
- [ ] Did any new dependency appear?
|
|
- [ ] Did any path or convention drift from repo standards?
|
|
|
|
## Required final response
|
|
|
|
```md
|
|
## Completed
|
|
|
|
## Changed files
|
|
|
|
## Commands run
|
|
|
|
## Test results
|
|
|
|
## Self-review
|
|
|
|
## Known limitations
|
|
|
|
## Next pass
|
|
```
|
|
|
|
## Scoring
|
|
|
|
Score each from 0-10:
|
|
|
|
- Scope control.
|
|
- Architecture consistency.
|
|
- Backend correctness.
|
|
- Frontend correctness, if applicable.
|
|
- GIS correctness.
|
|
- Test coverage.
|
|
- Documentation completeness.
|
|
- Release readiness.
|