Gabeujin Harness Code Review Pipeline
Use this skill after each chunk of code work and before considering the task complete.
Required Stages
- Extract review criteria from the active plan, review notes, and workspace conventions.
- Run relevant automated checks:
- build or type checks
- linting if configured
- targeted tests
- UTF-8 integrity for changed text artifacts
- Validate boundary conditions and likely runtime exception paths.
- Check environment compatibility, including framework/runtime versions such as Java/JDK when relevant.
- Audit newly added or changed dependencies for conflicts with the existing system.
- Review maintainability: SOLID, duplication, abstraction level, constants instead of hardcoding, and business/data-access separation.
- Confirm generator self-correction includes uncertainty where evidence is weak.
- Confirm atomic commit scope for each chunk or remediation.
- Run an implementation-independent code review.
- Highlight missing or weak test coverage.
- Apply remediation and re-run the relevant checks until the chunk is clean.
Review Priorities
- security and data integrity
- correctness and regressions
- test coverage and verification depth
- performance and maintainability
- style and consistency
Exit Rule
Do not close the chunk until critical and important findings are resolved, relevant tests pass, and governance artifacts reflect the final state.