jchildree

Create, review, audit, and list Architectural Decision Records for any software project. Trigger on: "create an ADR", "document this decision", "ADR for...", "what ADRs exist", "review this ADR", "update INDEX.md", architectural trade-offs, or design pivots affecting multiple layers or files. Project-agnostic -- works with any tech stack. Backed by Karpathy principles: think before deciding, simplest sufficient ADR, surgical scope.

Audit Codex skills for visibility flags, deterministic vs non-deterministic steps, and composability opportunities. Reads .Codex/skills/ (or a user-specified path), produces a punch list per skill, then shows proposed rewrites with a changelog. Trigger on: "audit my skills", "review my skill files", "which skills auto-fire?", "find duplicated logic in my skills", "should any skills be internal-only?", or any request to review, improve, or rationalize a set of SKILL.md files. Never modifies any file -- proposes changes and waits for approval.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Decision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is caveman-compressed so the tool-result injected back into main context is ~60% smaller -- main context lasts longer across long sessions. Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/reviewer", "save context", "compressed agent output".

Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

Compress natural language memory files (AGENTS.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman-compress FILEPATH or "compress memory file"

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Use when executing implementation plans with independent tasks in the current session

Convert Claude's persisted memory into a structured high-level outline and save it to the project Obsidian vault. Use to archive and organize accumulated session knowledge as a navigable vault note.

Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.

Set up and operate an LLM-maintained personal knowledge base wiki. Use when building a persistent, compounding knowledge base from source documents -- articles, papers, notes, transcripts, or any source material.

Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Use when the user wants a plan or design stress-tested before implementation, or asks to be grilled, interviewed, or interrogated about a decision tree.

Disciplined root-cause investigation for hard bugs and performance regressions, with findings pinned to the case board. Use when user reports a bug, says something is broken/throwing/failing, describes a performance regression, or asks to diagnose/debug/investigate something.

Use when writing a commit message — "write a commit", "commit message", "generate commit", "/commit", or invokes /faceless-commit, or when staging changes. Legacy alias: "/caveman-commit".

Use when reviewing code or a diff — "review this PR", "code review", "review the diff", "/review", or invokes /faceless-review. Legacy alias: "/caveman-review".

Use when the user wants terse, compressed, low-token responses — "faceless mode", "talk faceless", "be brief", "less tokens", "compress", or invokes /faceless. Also when token efficiency is explicitly requested. Legacy aliases: "caveman mode", "use caveman".

Use when turning raw material — research, notes, interview answers, fragments, or investigation findings — into a sourced written report or article, or when shaping, drafting, restructuring, or tightening such a draft. Triggers: "write up the findings", "investigative report", "turn these notes into an article", "draft the report", "shape this into an article", "edit the article", "help me write this up".

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `investigate`, `tdd`, `improve-codebase-architecture`, or `zoom-out` -- or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

Use when encountering environment, config, infrastructure, CI, or build issues -- not application-layer bugs (use investigate for those). Requires root cause investigation before any fix.