/simple
**Read-only code quality analysis for small to medium changes.**
$ npx -y skills add dcouple/Pane --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/simple
Context preview
What this command does when you run it.
**Read-only code quality analysis for small to medium changes.**
Command definition
simple.mdSimple Refactor
**Read-only code quality analysis for small to medium changes.**
Safe to run anytime. Analyzes code against codebase patterns and writes refactor plan without modifying files.
What This Does
Fast, focused code quality analysis that: 1. Classifies your changes (size, type, complexity) 2. Checks applicable patterns from CLAUDE.md files 3. Identifies code smells and pattern violations 4. Generates refactor plan with auto-fixable and manual issues 5. Writes plan to `./tmp/` for review
When to Use
- **Small changes** (2-5 files, 50-200 lines)
- **Medium changes** (5-10 files, 200-500 lines)
- **Bug fixes** and **enhancements**
- Quick pre-PR quality check
For large features (>10 files, >500 lines), use `/deep-refactor` instead.
Process
1. Classify Changes
git diff main --name-status
git diff main --numstat
git diff main --stat
**Determine:**
- **Size**: Tiny (<50) | Small (50-200) | Medium (200-500)
- **Type**: Bug Fix | Enhancement | Refactor
- **Complexity**: Trivial | Simple | Moderate
- **Layers**: Backend | Frontend | Both
2. Select Applicable Patterns
**Pattern Matrix:**
- **Tiny/Bug Fix** → Universal patterns only (imports, errors)
- **Small/Enhancement** → Universal + Basic architecture
- **Medium** → Universal + Architecture + Documentation (new files)
**Universal Patterns (Always Checked):**
- Zero relative imports (`../` is a bug)
- Proper error handling
- No commented-out code
- No TODOs without context
**Architecture Patterns (Medium+):**
- Controller-service separation
- BaseService extension
- TanStack Query for server state
- Proper hook patterns
3. Analyze Files
**Read changed files:**
git diff main --name-only
**Check patterns from:**
- `CLAUDE.md` - Import conventions, monorepo structure
- `apps/api/CLAUDE.md` - Backend architecture (authenticatedHandler, BaseService, ApiError)
- `apps/webapp/CLAUDE.md` - Frontend architecture (thin pages, orchestration hooks)
- `apps/webapp/src/hooks/CLAUDE.md` - TanStack Query patterns, query keys
- `apps/webapp/src/components/CLAUDE.md` - Component patterns
**Study exemplar files:**
- Controller: `apps/api/src/modules/feed/controllers/feed.controller.ts`
- Service: `apps/api/src/modules/feed/services/feed.service.ts`
- Page: `apps/webapp/src/app/(protected)/workspaces/[workspaceId]/feed/page.tsx`
- Hook: `apps/webapp/src/app/(protected)/workspaces/[workspaceId]/archive/useArchivePage.ts`
4. Detect Code Smells
**Universal Smells:**
- ❌ Relative imports (`../`, `../../`) - codebase has ZERO
- ❌ Long functions (>100 lines)
- ❌ Deep nesting (>3 levels)
- ❌ Magic numbers/strings
- ❌ Missing error handling
- ❌ Unused imports/variables
- ❌ Missing file-level documentation
**Backend Smells:**
- ❌ Business logic in controllers (should be in services)
- ❌ Controllers not using `authenticatedHandler` wrapper
- ❌ Services not extending `BaseService` when using DB
- ❌ Services not throwing `ApiError` for errors
- ❌ Multiple responsibilities in one service (SRP violation)
**Frontend Smells:**
- ❌ Business logic in pages (should be in hooks)
- ❌ Direct API calls instead of TanStack Query
- ❌ Hooks returning JSX (hooks return data/functions only)
- ❌ Missing `'use client'` directive
- ❌ Query mutations not invalidating related queries
- ❌ Local code NOT in underscore folders (`_components/`, `_hooks/`, `_types/`)
- ❌ Shared code used in only one place
**Configuration Object Pattern Violations:**
- ❌ Multiple similar functions (e.g., `formatTime`, `formatTimeCompact`) → consolidate with options
- ❌ Similar hooks with slight variations (e.g., `useGetItems`, `useGetArchivedItems`) → consolidate with options
- ❌ Importing multiple utilities for same purpose (e.g., `formatDistanceToNow` + custom `formatRelativeTime`)
- ❌ Duplicate interface/type definitions across files → single source of truth
- ❌ Similar services with minor differences → consolidate with configuration
5. Generate Report
Write refactor plan to `./tmp/simple-refactor-plan-[timestamp].md`:
# Simple Refactor Plan
## Classification
- Size: [X]
- Type: [X]
- Complexity: [X]
- Patterns Applied: [List]
## Quality Score: X/10
## Issues Found
### Critical (Must Fix)
- [file:line] Description
→ Fix: How to fix
→ Auto-fixable: Yes/No
### Warnings (Should Fix)
- [file:line] Description
→ Suggestion: Improvement
→ Auto-fixable: Yes/No
### Info (Nice to Have)
- [file:line] Suggestion
## Auto-Fixable Issues: X
- Convert relative imports to @/ aliases
- Remove unused imports
- Fix formatting issues
## Manual Fixes Required: Y
- [Specific issues requiring human judgment]
## Pattern Compliance
✓/✗ Import conventions
✓/✗ Controller-service separation
✓/✗ TanStack Query usage
✓/✗ File documentation
## Recommendations
1. Run `/refactor-apply --plan=./tmp/simple-refactor-plan-[TS].md --auto-only`
2. Manually fix [specific issues]
3. Re-run `/simple-refactor` to verify improvements
## References
Similar patterns to study:
- [Exemplar file paths from codebase]
Documentation:
- Backend patterns: `apps/api/CLAUDE.md`
- Frontend patterns: `apps/webapp/CLAUDE.md`
- Hook patterns: `apps/webapp/src/hooks/CLAUDE.md`
6. Show Next Steps
**Show results:**
📊 Analysis complete!
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Plan written to: ./tmp/simple-refactor-plan-[timestamp].md
Quality Score: X/10 (target: 9.8)
Auto-fixable: X issues
Manual fixes: Y issues
Issues found:
- [Critical issues summary]
- [Warnings summary]
Would you like me to run `/refactor-apply` to implement the fixes?
(This will apply auto-fixable changes and guide you through manual fixes)
**IMPORTANT:** Always ask the user before proceeding with fixes. Do not automatically run refactor-apply.
Critical Patterns (Verified from Codebase)
These patterns are enforced by reading the CLAUDE.md files:
1. **Zero relative imports** - Any `../` is a bug (verified via grep) 2. **authenticatedHandler
Read more
Simple Refactor
**Read-only code quality analysis for small to medium changes.**
Safe to run anytime. Analyzes code against codebase patterns and writes refactor plan without modifying files.
What This Does
Fast, focused code quality analysis that: 1. Classifies your changes (size, type, complexity) 2. Checks applicable patterns from CLAUDE.md files 3. Identifies code smells and pattern violations 4. Generates refactor plan with auto-fixable and manual issues 5. Writes plan to `./tmp/` for review
When to Use
- **Small changes** (2-5 files, 50-200 lines)
- **Medium changes** (5-10 files, 200-500 lines)
- **Bug fixes** and **enhancements**
- Quick pre-PR quality check
For large features (>10 files, >500 lines), use `/deep-refactor` instead.
Process
1. Classify Changes
git diff main --name-status git diff main --numstat git diff main --stat
**Determine:**
- **Size**: Tiny (<50) | Small (50-200) | Medium (200-500)
- **Type**: Bug Fix | Enhancement | Refactor
- **Complexity**: Trivial | Simple | Moderate
- **Layers**: Backend | Frontend | Both
2. Select Applicable Patterns
**Pattern Matrix:**
- **Tiny/Bug Fix** → Universal patterns only (imports, errors)
- **Small/Enhancement** → Universal + Basic architecture
- **Medium** → Universal + Architecture + Documentation (new files)
**Universal Patterns (Always Checked):**
- Zero relative imports (`../` is a bug)
- Proper error handling
- No commented-out code
- No TODOs without context
**Architecture Patterns (Medium+):**
- Controller-service separation
- BaseService extension
- TanStack Query for server state
- Proper hook patterns
3. Analyze Files
**Read changed files:**
git diff main --name-only
**Check patterns from:**
- `CLAUDE.md` - Import conventions, monorepo structure
- `apps/api/CLAUDE.md` - Backend architecture (authenticatedHandler, BaseService, ApiError)
- `apps/webapp/CLAUDE.md` - Frontend architecture (thin pages, orchestration hooks)
- `apps/webapp/src/hooks/CLAUDE.md` - TanStack Query patterns, query keys
- `apps/webapp/src/components/CLAUDE.md` - Component patterns
**Study exemplar files:**
- Controller: `apps/api/src/modules/feed/controllers/feed.controller.ts`
- Service: `apps/api/src/modules/feed/services/feed.service.ts`
- Page: `apps/webapp/src/app/(protected)/workspaces/[workspaceId]/feed/page.tsx`
- Hook: `apps/webapp/src/app/(protected)/workspaces/[workspaceId]/archive/useArchivePage.ts`
4. Detect Code Smells
**Universal Smells:**
- ❌ Relative imports (`../`, `../../`) - codebase has ZERO
- ❌ Long functions (>100 lines)
- ❌ Deep nesting (>3 levels)
- ❌ Magic numbers/strings
- ❌ Missing error handling
- ❌ Unused imports/variables
- ❌ Missing file-level documentation
**Backend Smells:**
- ❌ Business logic in controllers (should be in services)
- ❌ Controllers not using `authenticatedHandler` wrapper
- ❌ Services not extending `BaseService` when using DB
- ❌ Services not throwing `ApiError` for errors
- ❌ Multiple responsibilities in one service (SRP violation)
**Frontend Smells:**
- ❌ Business logic in pages (should be in hooks)
- ❌ Direct API calls instead of TanStack Query
- ❌ Hooks returning JSX (hooks return data/functions only)
- ❌ Missing `'use client'` directive
- ❌ Query mutations not invalidating related queries
- ❌ Local code NOT in underscore folders (`_components/`, `_hooks/`, `_types/`)
- ❌ Shared code used in only one place
**Configuration Object Pattern Violations:**
- ❌ Multiple similar functions (e.g., `formatTime`, `formatTimeCompact`) → consolidate with options
- ❌ Similar hooks with slight variations (e.g., `useGetItems`, `useGetArchivedItems`) → consolidate with options
- ❌ Importing multiple utilities for same purpose (e.g., `formatDistanceToNow` + custom `formatRelativeTime`)
- ❌ Duplicate interface/type definitions across files → single source of truth
- ❌ Similar services with minor differences → consolidate with configuration
5. Generate Report
Write refactor plan to `./tmp/simple-refactor-plan-[timestamp].md`:
# Simple Refactor Plan ## Classification - Size: [X] - Type: [X] - Complexity: [X] - Patterns Applied: [List] ## Quality Score: X/10 ## Issues Found ### Critical (Must Fix) - [file:line] Description → Fix: How to fix → Auto-fixable: Yes/No ### Warnings (Should Fix) - [file:line] Description → Suggestion: Improvement → Auto-fixable: Yes/No ### Info (Nice to Have) - [file:line] Suggestion ## Auto-Fixable Issues: X - Convert relative imports to @/ aliases - Remove unused imports - Fix formatting issues ## Manual Fixes Required: Y - [Specific issues requiring human judgment] ## Pattern Compliance ✓/✗ Import conventions ✓/✗ Controller-service separation ✓/✗ TanStack Query usage ✓/✗ File documentation ## Recommendations 1. Run `/refactor-apply --plan=./tmp/simple-refactor-plan-[TS].md --auto-only` 2. Manually fix [specific issues] 3. Re-run `/simple-refactor` to verify improvements ## References Similar patterns to study: - [Exemplar file paths from codebase] Documentation: - Backend patterns: `apps/api/CLAUDE.md` - Frontend patterns: `apps/webapp/CLAUDE.md` - Hook patterns: `apps/webapp/src/hooks/CLAUDE.md`
6. Show Next Steps
**Show results:**
📊 Analysis complete! ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Plan written to: ./tmp/simple-refactor-plan-[timestamp].md Quality Score: X/10 (target: 9.8) Auto-fixable: X issues Manual fixes: Y issues Issues found: - [Critical issues summary] - [Warnings summary] Would you like me to run `/refactor-apply` to implement the fixes? (This will apply auto-fixable changes and guide you through manual fixes)
**IMPORTANT:** Always ask the user before proceeding with fixes. Do not automatically run refactor-apply.
Critical Patterns (Verified from Codebase)
These patterns are enforced by reading the CLAUDE.md files:
1. **Zero relative imports** - Any `../` is a bug (verified via grep) 2. **authenticatedHandler
Repo: dcouple/Pane
Other commands on pane.
- /commit
Create git commits with user approval and no Claude attribution
Open command - /create_plan
You are tasked with creating detailed implementation plans through an interactive, iterative process. You should be skeptical, thorough, and work collaboratively with the user to produce high-quality technical specifications.
Open command - /describe_pr
Generate comprehensive PR descriptions following repository templates
Open command - /implement_plan
You are tasked with implementing an approved technical plan from `thoughts/shared/plans/`. These plans contain phases with specific changes and success criteria.
Open command - /iterate_plan
Iterate on existing implementation plans with thorough research and updates
Open command - /research_codebase
You are tasked with conducting comprehensive research across the codebase to answer user questions. You will spawn one or more parallel sub-agents to perform your reserach.
Open command

