Dev review changes
Skill ainova-systems/intelligence-dev-packs/packs/core/skills/dev-review-changes
Intelligence pack for software engineering based on Ainova Systems best practices
npx -y skills add ainova-systems/intelligence-dev-packs --skill dev-review-changesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 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
Read-only review of pending changes against project rules, with a severity verdict
SKILL.md
1.9 KB, as published. Nobody here has run it
Review Pending Changes
Read-only review before commit or PR - findings only, never edits.
Steps
- Enumerate:
git status --porcelain,git diff --stat. Diff = uncommitted changes plus commits ahead of the target branch (an explicit base ref overrides). Nothing changed - report and stop. - Load the rules that apply to the changed paths (project rules plus pack rules).
- Read the full diffs (
git diff,git diff --cached) AND the surrounding code - a locally clean change can still break a caller or violate a boundary. - Check, grouped by severity:
- Critical (block): correctness bugs; boundary/layering violations; secrets staged (
git-scan-secretspatterns); weakened gates (skipped tests, suppressions, lowered thresholds); new logic without tests; cross-cutting drift - grep every removed/renamed symbol across the tree. - Warning: convention violations, oversized files or diffs, duplicated helpers, missing validation at external boundaries.
- Suggestion: naming, comments restating code, extractable helpers.
- Critical (block): correctness bugs; boundary/layering violations; secrets staged (
- Verify each finding by re-reading the code - drop anything you cannot evidence.
- Report:
## Critical
- `path/file.ts:42` - <what> - <why / rule>
## Warning
...
## Suggestion
...
## Summary
- files: N, +A/-D; critical: N, warning: N, suggestion: N
- verdict: BLOCK | PASS-WITH-WARNINGS | CLEAN
Verify
- Every finding carries
file:lineplus evidence; a verdict is stated.
Scope / hand-off
- Fixing - the author/orchestrator; committing -
git-commit-push(a BLOCK verdict means fix first).
CRITICAL
- Read-only: never edit, stage, or commit.
- A diff mixing unrelated changes - the first finding is "split it".