Audit a repository for specification conflicts, logic defects, and security issues.
npx skills add https://github.com/sohei56/maul-team --skill cross-review-sohei56
Please help me install this Agent Skill. Skill: cross-review Source: https://github.com/sohei56/maul-team/tree/main/skills/cross-review Command: npx skills add https://github.com/sohei56/maul-team --skill cross-review-sohei56
This Skill provides a structured sprint-end integrity gate for detecting whole-repository defects that per-PBI reviews may miss, without destabilizing or reverting completed work.
Run the cross-review skill at the end of a Sprint after all PBIs have completed their per-PBI reviews and the merged main branch is available.
High-intent search queries and answers about installing and using this skill.
To catch repo-wide logic defects and security issues at the end of a sprint, run a whole-repository audit after per-PBI reviews. This analyzes the accumulated codebase at HEAD for specification conflicts, redundancy, and product-security vulnerabilities without reverting completed work.
A sprint-end integrity review is a structured audit gate applied after per-PBI quality checks. It coordinates static-analysis collection, audits the whole repository for defects, deduplicates findings, and routes actionable issues into draft PBIs for the next sprint.
You route defect triage findings into the next sprint backlog by synthesizing and deduplicating Critical and High audit issues, then automatically creating draft PBIs. This non-blocking approach moves reviewed PBIs to done while routing actionable defects forward.
Yes, you need passing application builds and tests before running a codebase audit. You also need the Sprint base commit, Scrum state and backlog files, and a configured or fallback static-analysis toolchain to execute the sprint-end integrity review successfully.
Yes, you can use a fallback static-analysis toolchain if no custom configuration exists. The audit process runs configured or built-in analysis tools, normalizes their findings, and preserves the results to support the repository redundancy audit axis.
The best way to detect redundant code across a full repository is to perform a whole-repository audit at HEAD. By normalizing and preserving static-analysis findings, the audit specifically targets redundant code alongside specification conflicts and security issues.
sohei56Create and activate Sprint Developer teammates for Product Backlog Items.
sohei56Conduct Scrum Sprint Reviews and preserve remaining work as draft PBIs.
atusyCoordinate TDD subtasks and sprint cycles within AI-Agentic Scrum.
sohei56Audit the accumulated repository at HEAD for cross-cutting specification, logic, redundancy, documentation, and security defects.
