hoavdc/CodexKit / skills/codexkit-high-signal-review
codexkit-high-signal-review
VerifiedReview changes with a risk-first mindset that prioritizes bugs, regressions, missing tests, and operational gaps.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.1 KB |
| agents/openai.yaml | config | 210 B |
| examples/common-mistakes.md | markdown | 814 B |
| examples/good-output.md | markdown | 796 B |
| references/severity-rubric.md | markdown | 262 B |
| verification/checklist.md | markdown | 1.3 KB |
verification/checklist.md
View on GitHub# 4C Verification Checklist — High-Signal Review
> Use this checklist after generating output. Answer each question honestly.
## Correctness — Is it right?
- [ ] Every critique cites a specific line, paragraph, or section — not vague 'could be better'
- [ ] Technical claims in the review are verified against authoritative sources
- [ ] Suggested fixes are tested or proven patterns, not speculative improvements
## Completeness — Is it done?
- [ ] All major sections of the reviewed material are addressed
- [ ] Both strengths and weaknesses are documented
- [ ] Missing context or assumptions are flagged explicitly
## Context-fit — Does it match?
- [ ] Review depth matches the material's maturity (draft vs final)
- [ ] Terminology matches the author's domain (don't use dev terms for marketing docs)
- [ ] Feedback is actionable by the author — not requiring skills they don't have
## Consequence — Is it safe to use?
- [ ] If the author ignored all feedback, what is the worst outcome for the project?
- [ ] If the author implemented everything literally, could any suggestion cause harm?
- [ ] Would this review damage the working relationship if delivered as-is?
---
**Final question:** _If this output were used immediately in production, what is the single biggest risk?_
Write the answer here before considering the skill output complete.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |