Stats
Actions
Tags
From pact
Audits recent session changes against PACT cognitive redirections: dependency traces, staleness of docs/maps/trackers, cache consistency, package verification, lifecycle impacts.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pact:pact-checkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Review the changes made in this session against PACT's cognitive redirections. For each question, evaluate honestly:
Review the changes made in this session against PACT's cognitive redirections. For each question, evaluate honestly:
1. Dependency trace: For every file edited this session, what depends on it and what does it depend on? Were all downstream consumers updated?
2. Staleness audit: What did the changes make stale? Check:
3. Cache consistency: If any provider/state management was modified, were ALL caches updated (both list and map caches)?
4. Package verification: Were any packages used based on assumption rather than verified documentation? Check docs/reference/packages/ for knowledge files.
5. Lifecycle impact: Do the changes survive all app states? Fresh install, normal open, background, force close, backup restore?
Report findings as:
npx claudepluginhub jonathanmr22/pact --plugin pactFinal code review skill: runs stack-specific tests/lints (Next.js, Python, Swift, Kotlin), security checks, verifies spec.md criteria, audits hub files, issues ship/no-go verdict after /build or /deploy.
Reviews code changes from MRs/PRs, local commits, or uncommitted files for document compliance, content quality (architecture, tests, observability), and end-to-end consistency (User Story to observability).
Audits project configuration and documentation for drift, staleness, and broken references. Scans CLAUDE.md files, configs, plugin manifests, and knowledge files.