mays

dotfiles

Personal Claude Code configuration, packaged as an installable plugin (mays). One system: distill each repo's review culture into rules, write code against those rules from the first keystroke, gate every PR through layered review, and feed human feedback back into the rules.

The System

/onboard-repo                  # day one in a new codebase: CLAUDE.md + standards + permissions
── write code ──               # the load-standards hook injects .claude/standards.md at session start
/ship                          # pre-review → code-review high → tests → commit → push → PR
── after human review lands ──
/distill-standards #<PR>       # absorb that PR's feedback immediately
/distill-standards             # or: cheap delta over everything merged since the last run
── reviewing someone else's PR ──
/review-pr <PR# or URL>        # standards-aware review, optionally posted to GitHub

distill-standards reads PR review history via gh and writes distilled rules (never raw comments) to .claude/standards.md. Recurring feedback becomes conventions; substantive one-off feedback — edge cases, domain gotchas — lands in a ## One-offs section and gets promoted to a convention if it recurs. Bare runs do a delta over only the PRs merged since the last run, so standards stay current without re-mining history.

Standards apply at write time, not just review time: the load-standards SessionStart hook injects the file into context when a session opens in the repo, so code conforms on the first pass instead of being repaired at review.

/ship runs the whole pre-PR path with one confirmation checkpoint before anything leaves the machine, opening the PR with the summary + test-plan format from the ~/.claude/CLAUDE.md managed block. To run its gates individually:

/pre-review                    # standards conformance — catches what reviewers flagged before
/code-review high              # native correctness review — bugs, not style
/extreme-code-quality-review   # structural audit — only for large or structural changes

pre-review checks your branch against every rule (one-offs included) plus a baseline AI-slop checklist (obvious comments, gratuitous defensive checks, as any, single-use abstractions), then offers to apply the fixes. The goal: by the time a human sees the PR, their past feedback has already been addressed.

Every review surface consults .claude/standards.md when it exists: /pre-review, /review-pr, and /extreme-code-quality-review load it directly, and sync.sh maintains a managed block in ~/.claude/CLAUDE.md so the native /code-review picks it up in any repo.

New codebase? /onboard-repo bootstraps all of this on day one: surveys the repo, writes a real CLAUDE.md, runs the full distill, and proposes a toolchain-matched permissions allowlist — with a choice between committing the files or keeping them local-only (.git/info/exclude + settings.local.json).

Install

From within Claude Code:

/plugin marketplace add stevenmays/dotfiles
/plugin install mays@dotfiles

Then sync personal settings (optional, overwrites ~/.claude/settings.json):

./sync.sh

Update

After new commits land in this repo, refresh the marketplace catalog — Claude Code re-pulls the source and upgrades the installed mays plugin in the same step:

/plugin marketplace update dotfiles

Then run /reload-plugins when prompted (or restart Claude Code) to load the new version. To make this automatic, enable auto-update for the marketplace under /plugin → Marketplaces → dotfiles.

Non-interactive equivalent:

claude plugin marketplace update dotfiles

What's in the Plugin

Commands

Command	Purpose
/distill-standards [N | #PR | full]	Mine merged PRs into .claude/standards.md — full regen from N PRs, delta since last run (no args), or absorb a single PR's feedback
/extreme-code-quality-review	Extremely strict maintainability audit of the current branch, standards-aware
/fix-merge-conflict	Resolve merge conflicts non-interactively
/onboard-repo [N]	Day-one bootstrap for a new codebase — CLAUDE.md, distilled standards, and a permissions allowlist in one run
/pre-review	Check the branch diff against distilled standards (with staleness warning), then offer to apply fixes
/review-pr <PR#>	Review someone else's PR against distilled standards; optionally post findings to GitHub
/security-audit	Audit home-directory dotfiles for security issues (read-only report)
/ship	The golden path as one command: pre-review → code-review → tests → commit → push → PR
/test-and-fix	Run tests and fix failures until green (also /ship's test gate)

Skills