agentsclimarketplace

Phase review

Skill yarlson/yarstack/plugins/yarstack/skills/phase-review

Engineering workflows and standards for Codex and Claude Code: plan, implement, test, review, and deliver repository changes.

Install
npx -y skills add yarlson/yarstack --skill phase-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Review one validated phase for behavior-preserving structural regressions introduced or materially worsened by the change. Use after phase validation and before final delivery.

SKILL.md

1.6 KB, as published. Nobody here has run it

Phase Structural Review

Own a narrow maintainability pass after correctness has been established.

Workflow

  1. Read the selected contract, applicable repository rules, final diff, and changed units.
  2. Identify only complexity, duplication, unclear ownership, loose types, or unnecessary indirection introduced or materially worsened by the selected change.
  3. Use crap-index-assess when the repository's configured CRAP check covers changed methods or the phase was intended to reduce their CRAP risk. Treat score changes as supporting evidence, not a structural verdict.
  4. Fix a finding only when the parent implementation request authorizes scoped edits and the correction is clearly behavior-preserving.
  5. Report a worthwhile correction when it requires non-trivial restructuring or broader authority; do not expand scope during the review.
  6. Rerun affected checks after every edit.

Correctness belongs to phase-validate; general read-only defect review to code-review; test sufficiency to test-gap-review; documentation accuracy to docs-drift-review; and specialized risks to their owning reviewers.

Do not add behavior, pursue unrelated cleanup, use subjective file-size thresholds, or continue until no imaginable simplification remains.

Finish when structural regressions introduced by the change are fixed or reported with their scope and risk.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.