jcdendrite/claude-config

Status: stable — actively maintained.
Portable Claude Code global configuration: custom skills, PreToolUse hooks that gate git commit and PR-comment flows, and a custom statusline. Runs on any Unix-like system (Linux, macOS, WSL). Managed with GNU Stow.
Install it to wire in a set of pre-built hooks that gate commits, pushes, and PR comments until explicit review steps are satisfied; a full contribution pipeline from /plan-it through /respond-pr; a roster of specialist reviewer agents auto-triggered from code review; and a three-tier private-project redaction system that blocks sensitive identifiers before they land in public commits. See Philosophy for the design rationale.
Maintained by Cordova Strategy.
## Table of Contents
Philosophy
Docs
Quickstart
Updating after git pull
Requirements
What this installs
Configuration
Worktree enforcement
Autonomous shipping
PR cost disclosure
Prose tightening pass
Permission-prompt tracking
Repo relocation
Private-project redaction
Auto mode
Output preferences
Machine-specific overrides
Artifact and Workflow disabled by default
Context management
Tests
Acknowledgments
License
## Philosophy
### Why this repo exists
Working across a variety of projects from very early stage to enterprise-level, I wanted to use a flexible but predictable setup for Claude Code to help me get through large chunks of work efficiently and cost-effectively: from security audits of vibe-coded codebases to building out standard features, adding testing infrastructure, and enforcing quality against industry-standard, best-practice checklists. I wanted to stop fixing the same errors that AI agents kept encountering and really focus my time on the nuanced technical challenges that need human judgment.
### How this repo is different from others
AI agents are powerful but probabilistic. They will frequently gaslight you, or more fairly put, they will confidently draw incorrect conclusions from prose (even top-class models). Simply stated, unsupervised AI is reliable for summarization but not synthesis. I wanted to add a layer of determinism on top of agents' inherently probabilistic judgment to enforce quality and prevent repetitive errors where I could. To achieve these goals, I added safeguards in this repo with hooks and markers.
I also wanted to encode industry-standard best practices in this repo. LLMs are trained on the corpus of the internet and are biased by the loudest and most common viewpoints. While the wisdom of the masses can often be directionally correct, it's best to defer to primary sources and scientific thinking, applying the rigor of research and adhering to evidence-based approaches. You'll see those perspectives represented in the content of the skills and instructions in this repo, with references to primary sources that converge on tried-and-true guidelines on how to design and write good software.
### How enforcement complements instructions
Claude Code without enforcement will claim code is done before tests pass, skip the review step when it judges a change "too small," write to the main worktree when a concurrent session is already staged there, and paste project codenames directly into commit messages and PR bodies. claude-config makes these mistakes structurally impossible rather than relying on prompt instructions.