Jonathan

Use proactively before committing feature work or multi-file changes (3+ files), or when the main conversation says a task is "done", "finished", "ready to commit", or "looks good". Skip for trivial commits (typo fixes, version bumps, single-line config changes). Runs PACT's governance checklist in an isolated context so the main session gets an honest second opinion without the cognitive load of self-review.

Initialize PACT governance files in the current project

Use proactively before editing files that appear in SYSTEM_MAP.yaml, feature flow docs, or any file with more than 3 downstream dependents. Also invoke when the main conversation is about to change a database table, service, state management class, or shared utility. Traces dependency chains and returns a concrete impact report so the main session edits with full awareness of what will break.

Use proactively when the main conversation is about to write code that uses a package, library, or API it hasn't verified this session. Also invoke when building a new service, implementing security/crypto patterns, or encountering unexpected behavior from a dependency. Checks existing PACT knowledge files first, researches if needed, and saves synthesis back to the knowledge system so future sessions inherit the findings.

Run PACT cognitive redirections against recent changes

Generate a lifecycle flow document for a feature

Log a bug investigation using PACT's structured bug tracker

Search PACT's vector memory for relevant bugs, solutions, research, and feedback