tony

Riper Workflow — Git skill for Claude Code

Git community intermediate

by Tony Narlock - Structured development workflow enforcing separation between Research, Innovate, Plan, Execute, and Review phases.

How to install Riper Workflow

This entry records only its repository, not the path inside it, so there is no exact command to give. Open tony/claude-code-riper-5 and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Riper Workflow does

**R**esearch • **I**nnovate • **P**lan • **E**xecute • **R**eview

Alternatives in Git

Analysis Claude Code — GitHub Repo stars Complete reverse engineering research and analysis of Claude Code v1.0.33 Reverse engineerin 35k ★
Triage Issues — Triage open GitHub issues — split into bugs vs features, rank by severity/opportunity, and flag under-specifie 12.6k ★
Fullstack Dev Skills — by jeffallan - A comprehensive Claude Code plugin with 65 specialized skills covering full-stack development a 7k ★

README

RIPER Workflow for Claude Code

**R**esearch • **I**nnovate • **P**lan • **E**xecute • **R**eview

A structured, context-efficient development workflow for [Claude Code](https://github.com/anthropics/claude-code/) using [custom slash commands](https://docs.anthropic.com/en/docs/claude-code/slash-commands#custom-slash-commands) and [subagents](https://docs.anthropic.com/en/docs/claude-code/sub-agents).

🎯 Overview

RIPER creates a controlled, guided flow that enforces separation between research, planning, and execution phases. This helps:

Reduce context usage through specialized agents
Prevent premature implementation before understanding
Maintain clear documentation of decisions
Enable reproducible development processes

🚀 Quick Start

Installation

Copy the .claude directory to your project root:

cp -r .claude /path/to/your/project/

Update `.claude/project-info.md` with your project details
Customize `.claude/riper-config.json` with your tech stack and paths
Optional: Add `.claude/memory-bank/` to `.gitignore` to keep plans and reviews private:
```
echo ".claude/memory-bank/" >> .gitignore
```
Or selectively ignore just plans and reviews while keeping memory bank structure:
```
echo ".claude/memory-bank/*/plans/" >> .gitignore
```
```
echo ".claude/memory-bank/*/reviews/" >> .gitignore
```
Note: If you accidentally commit these, remove them before merging:
```
git rebase -i HEAD~n  # where n is number of commits to review
```

Basic Usage

Start a guided RIPER session:

/riper:strict

Then use the workflow commands:

**Research** - Investigate the codebase

/riper:research analyze authentication system

**Plan** - Create technical specifications
```
/riper:plan add OAuth2 support
```
**Execute** - Implement the approved plan
```
/riper:execute
```
Or execute a specific substep:

...