drewdrewthis

61 mods across 2 repositories, 7 stars between them.

deep-reflect

25

drewdrewthis/claude-skills

Skill Claude CodeCodex

Deep audit of Claude session history. Analyzes JSONL logs for mistakes, failed patterns, token waste, and missed opportunities. Writes findings to memory.

2 4mo ago B 35 tokens

deep-think

26

drewdrewthis/claude-skills

Skill Claude CodeCodex

Structured design exploration for open-ended technical questions. Combines codebase analysis, external research, strategy generation, and adversarial debate to produce a decision-ready report saved to docs/research/. Use when facing 'how should we...', 'what's the best way to...', 'deep think about', or any design…

2 4mo ago A 71 tokens

drive-pr

27

drewdrewthis/claude-skills

Skill Claude CodeCodex

Drive a PR to mergeable state — fix CI failures and address review comments. Loops until green.

2 4mo ago A 24 tokens

evolve-skill

28

drewdrewthis/claude-skills

Skill Claude CodeCodex

Improve a skill based on how it just performed. Analyzes conversation for friction, corrections, wasted tokens, and missed steps, then patches the skill. Auto-invoke after any skill completes. Also triggered by /deep-reflect when it identifies skills that were used.

2 4mo ago A 59 tokens

fix-bug

29

drewdrewthis/claude-skills

Skill Claude CodeCodex

Bug fix flow: readiness check → investigate → failing test (TDD) → fix → verify → review → complete. Skips planning — fixes existing behavior, not new behavior.

2 4mo ago A 40 tokens

implement

30

drewdrewthis/claude-skills

Skill Claude CodeCodex

Start implementation of a GitHub issue. Usage: /implement #123 or /implement.

2 4mo ago A 23 tokens

investigate

31

drewdrewthis/claude-skills

Skill Claude CodeCodex

Systematic investigation of a production bug or performance issue. Traces symptoms to root cause through code analysis, hypothesis testing, and empirical validation.

2 4mo ago A 31 tokens

launch

32

drewdrewthis/claude-skills

Skill Claude CodeCodex

Create a worktree for a GitHub issue and launch a Claude session to implement it. One command: worktree + session.

2 4mo ago A 28 tokens

learn

33

drewdrewthis/claude-skills

Skill Claude CodeCodex

Learn from mistakes by updating project guidelines. Use when a mistake was made that should be prevented in future sessions.

2 4mo ago A 24 tokens

log-mistake

34

drewdrewthis/claude-skills

Skill Claude CodeCodex

Log a mistake to the structured mistake log. Use when the user corrects you, when you catch your own mistake, or when /learn codifies a new rule.

2 4mo ago A 39 tokens

optimize

35

drewdrewthis/claude-skills

Skill Claude CodeCodex

Audit agent config and conversation for token waste: duplication, bloat, unnecessary context loading. Produces actionable fixes.

2 4mo ago A 26 tokens

coder

36

drewdrewthis/claude-skills

Agent

Implementation agent. Receives pre-written failing tests and makes them pass. Does NOT run tests itself — the orchestrator handles validation.

2 4mo ago A 28 tokens

devils-advocate

37

drewdrewthis/claude-skills

Agent

Use this agent when the user presents an architecture proposal, system design, implementation plan, technical idea, or code approach and wants it stress-tested before committing to implementation. This includes RFC reviews, ADR drafts, feature planning, migration strategies, API designs, data model proposals, or any…

2 4mo ago A 428 tokens

hygiene-reviewer

38

drewdrewthis/claude-skills

Agent

Codebase-aware reviewer that checks for reuse, existing patterns, dead code, bloat, idioms, and boy scout rule. The core question: does this code fit well in the codebase?

2 4mo ago A 46 tokens

principles-reviewer

39

drewdrewthis/claude-skills

Agent

Opinionated design reviewer focused on SRP, readability, extensibility, and simplicity. The core question: is this well-designed code that the next engineer can understand in 30 seconds?

2 4mo ago A 42 tokens

security-reviewer

40

drewdrewthis/claude-skills

Agent

Adversarial reviewer scanning for PII exposure, hardcoded secrets, and sensitive data leaks. The core question: can this code hurt someone?

2 4mo ago A 33 tokens

test-reviewer

41

drewdrewthis/claude-skills

Agent

Reviews tests for pyramid placement, coverage, naming, quality, and efficiency. The core question: are these tests at the right level, testing the right things, and running efficiently?

2 4mo ago A 40 tokens

code

42

drewdrewthis/claude-skills

Skill Claude CodeCodex

Delegate implementation work to the coder agent. Provide requirements or feature file path.

2 4mo ago A 17 tokens

deliver-work

43

drewdrewthis/claude-skills

Skill Claude CodeCodex

Implementation and verification phase. Runs implement → sweep → review → prove-it → complete. Takes a validated feature file from /plan-work and delivers a green PR. Use when the plan is ready and you just need to build it.

2 4mo ago A 49 tokens

intent

44

drewdrewthis/claude-skills

Skill Claude CodeCodex

Metacognitive checkpoint — analyze user intent before executing. Use standalone or let orchestrate/plan invoke it. Forces critical thinking about what the user actually wants.

2 4mo ago A 34 tokens

orchestrate

45

drewdrewthis/claude-skills

Skill Claude CodeCodex

Classify work as bug/feature/refactor, run planning, create tasks from every acceptance criterion, then hand off to implementation. The task list is the contract.

2 4mo ago A 37 tokens

plan-feature

46

drewdrewthis/claude-skills

Skill Claude CodeCodex

Create a feature file with acceptance criteria before implementation. Use when no specs/features/.feature file exists for the work.

2 4mo ago A 26 tokens

plan-work

47

drewdrewthis/claude-skills

Skill Claude CodeCodex

Research and planning phase for features. Runs intent → plan → challenge → readiness gate. Produces a validated feature file ready for /deliver-work. Use before implementation when the problem needs thinking, not just coding.

2 4mo ago A 45 tokens

prove-it

48

drewdrewthis/claude-skills

Skill Claude CodeCodex

Prove implementation correctness by mapping every acceptance criterion to concrete evidence (passing tests, command output, code grep). Use after /review passes, before marking a PR ready. Also use standalone when you want proof that work is actually done — not just 'I think it works.'.

2 4mo ago A 58 tokens