By jonathanmr22
Enforces governance for AI coding agents on projects: audits diffs for missed documentation and dependency impacts, traces dependency chains before edits, blocks dangerous tool calls outside branch policies, logs structured bug investigations, and indexes project knowledge via semantic search.
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.
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.
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.
Log a bug investigation using PACT's structured bug tracker
Run PACT cognitive redirections against recent changes
Generate a lifecycle flow document for a feature
Initialize PACT governance files in the current project
Search PACT's vector memory for relevant bugs, solutions, research, and feedback
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Uses Bash, Write, or Edit tools
Uses Bash, Write, or Edit tools
A framework for governing AI coding agents through infrastructure instead of instructions.
The common assumption is that Claude's problem is memory. It forgets facts, decisions, and other nuances between sessions, so the go-to "solution" is to make it remember more by applying bandaids like session logs or plans in endless markdown files, classic databases, spawning dozens of subagents to argue it out with little context, and attempting marathon sessions to prove you've avoided compaction; that last one is actually nightmare fuel, not an accomplishment. I'll take "context rot" for $500, Alex.
The uncomfortable truth is that Claude makes bad decisions even when it remembers everything. It will edit a file it hasn't read. Fix one layer and break three downstream. Guess at a package API instead of checking docs. Declare "done" while half the work is missing. Full context doesn't fix any of these. They're reasoning failures, not recall failures.
Memory plugins ask: "How do we help Claude remember?" PACT asks: "How do we help Claude think?"
Solo developers and small teams. PACT was built by a solo developer for solo developers, then designed to scale up. The smaller your team, the more you need it. There's no code reviewer to notice the stale cache, no teammate to check the dependency chain, no QA to catch the UI regression. Large teams have humans for that. You have PACT.
Small project? Good. PACT scales down with you — the Seed tier gives you reasoning quality without structural overhead, and delegation lets small projects inherit knowledge from a larger one or a shared stack-level instance. PACT's subsystems activate on the patterns they detect, not on project size.
PACT is a modular governance framework for AI coding agents (Claude Code, Cursor, Copilot Workspace, etc.). Use all of it or just the parts that fill gaps in your existing setup — if you already have a memory layer, a task manager, or a workflow orchestrator, PACT detects that and only scaffolds what's missing.
Every recommendation in Anthropic's Claude Prompting Best Practices guide is addressed by PACT — clear instructions, context with rationale, structured XML, role-setting, examples, anti-hallucination guards, investigation-before-answering mandates, state management, subagent orchestration, autonomy/safety balancing, and anti-overengineering. PACT was built from production failures before these were published as best practices.
PACT has twelve features. Take what you need:
npx claudepluginhub jonathanmr22/pact --plugin pactOrchestration harness that turns Claude Code into a coordinated team of specialist AI agents
Intelligent orchestration platform for AI coding tools — routes tasks to the best model, learns from outcomes, and enforces quality through multi-model consensus. 46 MCP tools for agent management, research, memory, consensus voting, codebase intelligence, and a full dev pipeline.
Personal Claude Code + Codex dev stack: security hooks, AI-first code conventions, /security-review, /repo-map, /stack-check, portable statusline. Designed to complement other skills-based plugins, not replace them.
Analyze and enforce best practices for AI coding agent projects. Assess codebase readiness across 8 pillars with /readiness, then scaffold enforcement with /setup: TDD, secret scanning, file size limits, auto-generated docs, and git hooks.
Check how well your repo supports AI coding agents.
Complete project development toolkit: 23 agents, 23 slash commands, 29 lifecycle hooks, and 69 reusable skills for Claude Code workflows