oh-my-claude-sisyphus 3.0.9 → 3.0.10

package/README.md

@@ -30,7 +30,7 @@
 
 **Step 2:** Run setup
 ```
-/omc-setup
+/oh-my-claudecode:omc-setup
 ```
 
 That's it. Everything else is automatic.

package/commands/analyze.md

@@ -1,3 +1,45 @@
 ---
 description: Deep analysis and investigation
 ---
+
+# Deep Analysis Mode
+
+[ANALYSIS MODE ACTIVATED]
+
+## Objective
+
+Conduct thorough analysis of the specified target (code, architecture, issue, bug, performance bottleneck, security concern).
+
+## Approach
+
+1. **Gather Context**
+   - Read relevant files
+   - Check git history if relevant
+   - Review related issues/PRs if applicable
+
+2. **Analyze Systematically**
+   - Identify patterns and antipatterns
+   - Trace execution flows
+   - Map dependencies and relationships
+   - Check for edge cases
+
+3. **Synthesize Findings**
+   - Root cause (for bugs)
+   - Design decisions and tradeoffs (for architecture)
+   - Bottlenecks and hotspots (for performance)
+   - Vulnerabilities and risks (for security)
+
+4. **Provide Recommendations**
+   - Concrete, actionable next steps
+   - Prioritized by impact
+   - Consider maintainability and technical debt
+
+## Output Format
+
+Present findings clearly:
+- **Summary** (2-3 sentences)
+- **Key Findings** (bulleted list)
+- **Analysis** (detailed explanation)
+- **Recommendations** (prioritized)
+
+Stay objective. Cite file paths and line numbers. No speculation without evidence.

package/commands/cancel-ralph.md

@@ -0,0 +1,41 @@
+---
+description: Cancel active Ralph (and linked ultrawork if auto-activated)
+---
+
+# Cancel Ralph
+
+[RALPH CANCELLED]
+
+Ralph has been cancelled. You MUST now deactivate the state files.
+
+## MANDATORY ACTION
+
+Execute this command to fully cancel ALL persistent modes:
+
+```bash
+mkdir -p .omc ~/.claude && \
+echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ralph"}' > .omc/ralph-state.json && \
+echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ralph", "linked_to_ralph": false}' > .omc/ultrawork-state.json && \
+echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ralph"}' > .omc/ralph-plan-state.json && \
+echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ralph"}' > ~/.claude/ralph-state.json && \
+echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ralph"}' > ~/.claude/ultrawork-state.json && \
+rm -f .omc/ralph-verification.json
+```
+
+After running this command, you are free to stop working. The persistent mode hook will no longer force continuation.
+
+## What Was Cancelled
+
+- **Ralph**: Self-referential completion loop
+- **Ultrawork**: Parallel execution mode (auto-activated with Ralph by default)
+- **Ralph Plan**: Iterative planning loop (if active via /ralplan)
+- **Verification State**: Any pending architect verification
+
+## Note on Linked Modes
+
+Since v3.0, Ralph automatically activates Ultrawork for parallel execution. When you cancel Ralph, the linked Ultrawork is also cancelled. If you started Ultrawork separately (not via Ralph), use `/cancel-ultrawork` to cancel it independently.
+
+## To Start Fresh
+
+- `/ralph "task"` - Start ralph with ultrawork (default)
+- `/ultrawork "task"` - Start ultrawork only (standalone)

package/commands/cancel-ultraqa.md

@@ -0,0 +1,27 @@
+---
+description: Cancel active UltraQA cycling workflow
+---
+
+# Cancel UltraQA
+
+[ULTRAQA CANCELLED]
+
+The UltraQA cycling workflow has been cancelled. Clearing state file.
+
+## MANDATORY ACTION
+
+Execute this command to cancel UltraQA:
+
+```bash
+mkdir -p .sisyphus && echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ultraqa"}' > .omc/ultraqa-state.json
+```
+
+After running this command, the QA cycling will stop.
+
+## To Start Fresh
+
+- `/ultraqa --tests` - Run until all tests pass
+- `/ultraqa --build` - Run until build succeeds
+- `/ultraqa --lint` - Run until no lint errors
+- `/ultraqa --typecheck` - Run until no type errors
+- `/ultraqa --custom "pattern"` - Run until pattern matches

package/commands/cancel-ultrawork.md

@@ -0,0 +1,40 @@
+---
+description: Cancel active Ultrawork mode
+---
+
+# Cancel Ultrawork
+
+[ULTRAWORK CANCELLED]
+
+The Ultrawork mode has been cancelled. Clearing state files.
+
+## MANDATORY ACTION
+
+**First**, check if ultrawork is linked to an active Ralph loop:
+
+```bash
+cat .omc/ultrawork-state.json 2>/dev/null | jq -r '.linked_to_ralph // false'
+```
+
+**If linked_to_ralph is true**: Use `/cancel-ralph` instead to cancel both Ralph and its linked Ultrawork.
+
+**Otherwise**, execute this command to cancel Ultrawork:
+
+```bash
+mkdir -p .omc && \
+echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ultrawork"}' > .omc/ultrawork-state.json && \
+echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ultrawork"}' > ~/.claude/ultrawork-state.json
+```
+
+After running this command, ultrawork mode will be deactivated and the HUD will update.
+
+## Note on Linked Modes
+
+Since v3.0, Ralph automatically activates Ultrawork. If you see `linked_to_ralph: true` in the ultrawork state, it means Ultrawork was auto-activated by Ralph. In this case:
+- Use `/cancel-ralph` to cancel both modes
+- If you only cancel ultrawork, Ralph will continue but without parallel execution benefits
+
+## To Start Fresh
+
+- `/ultrawork "task"` - Start ultrawork only (standalone)
+- `/ralph "task"` - Start ralph with ultrawork (default)

package/commands/deepinit.md

@@ -0,0 +1,319 @@
+---
+description: Deep codebase initialization with hierarchical AGENTS.md documentation
+---
+
+# Deep Init Skill
+
+Creates comprehensive, hierarchical AGENTS.md documentation across the entire codebase.
+
+## Core Concept
+
+AGENTS.md files serve as **AI-readable documentation** that helps agents understand:
+- What each directory contains
+- How components relate to each other
+- Special instructions for working in that area
+- Dependencies and relationships
+
+## Hierarchical Tagging System
+
+Every AGENTS.md (except root) includes a parent reference tag:
+
+```markdown
+<!-- Parent: ../AGENTS.md -->
+```
+
+This creates a navigable hierarchy:
+```
+/AGENTS.md                          ← Root (no parent tag)
+├── src/AGENTS.md                   ← <!-- Parent: ../AGENTS.md -->
+│   ├── src/components/AGENTS.md    ← <!-- Parent: ../AGENTS.md -->
+│   └── src/utils/AGENTS.md         ← <!-- Parent: ../AGENTS.md -->
+└── docs/AGENTS.md                  ← <!-- Parent: ../AGENTS.md -->
+```
+
+## AGENTS.md Template
+
+```markdown
+<!-- Parent: {relative_path_to_parent}/AGENTS.md -->
+<!-- Generated: {timestamp} | Updated: {timestamp} -->
+
+# {Directory Name}
+
+## Purpose
+{One-paragraph description of what this directory contains and its role}
+
+## Key Files
+{List each significant file with a one-line description}
+
+| File | Description |
+|------|-------------|
+| `file.ts` | Brief description of purpose |
+
+## Subdirectories
+{List each subdirectory with brief purpose}
+
+| Directory | Purpose |
+|-----------|---------|
+| `subdir/` | What it contains (see `subdir/AGENTS.md`) |
+
+## For AI Agents
+
+### Working In This Directory
+{Special instructions for AI agents modifying files here}
+
+### Testing Requirements
+{How to test changes in this directory}
+
+### Common Patterns
+{Code patterns or conventions used here}
+
+## Dependencies
+
+### Internal
+{References to other parts of the codebase this depends on}
+
+### External
+{Key external packages/libraries used}
+
+<!-- MANUAL: Any manually added notes below this line are preserved on regeneration -->
+```
+
+## Execution Workflow
+
+### Step 1: Map Directory Structure
+
+```
+Task(subagent_type="explore", model="haiku",
+  prompt="List all directories recursively. Exclude: node_modules, .git, dist, build, __pycache__, .venv, coverage, .next, .nuxt")
+```
+
+### Step 2: Create Work Plan
+
+Generate todo items for each directory, organized by depth level:
+
+```
+Level 0: / (root)
+Level 1: /src, /docs, /tests
+Level 2: /src/components, /src/utils, /docs/api
+...
+```
+
+### Step 3: Generate Level by Level
+
+**IMPORTANT**: Generate parent levels before child levels to ensure parent references are valid.
+
+For each directory:
+1. Read all files in the directory
+2. Analyze purpose and relationships
+3. Generate AGENTS.md content
+4. Write file with proper parent reference
+
+### Step 4: Compare and Update (if exists)
+
+When AGENTS.md already exists:
+
+1. **Read existing content**
+2. **Identify sections**:
+   - Auto-generated sections (can be updated)
+   - Manual sections (`<!-- MANUAL -->` preserved)
+3. **Compare**:
+   - New files added?
+   - Files removed?
+   - Structure changed?
+4. **Merge**:
+   - Update auto-generated content
+   - Preserve manual annotations
+   - Update timestamp
+
+### Step 5: Validate Hierarchy
+
+After generation, run validation checks:
+
+| Check | How to Verify | Corrective Action |
+|-------|--------------|-------------------|
+| Parent references resolve | Read each AGENTS.md, check `<!-- Parent: -->` path exists | Fix path or remove orphan |
+| No orphaned AGENTS.md | Compare AGENTS.md locations to directory structure | Delete orphaned files |
+| Completeness | List all directories, check for AGENTS.md | Generate missing files |
+| Timestamps current | Check `<!-- Generated: -->` dates | Regenerate outdated files |
+
+Validation script pattern:
+```bash
+# Find all AGENTS.md files
+find . -name "AGENTS.md" -type f
+
+# Check parent references
+grep -r "<!-- Parent:" --include="AGENTS.md" .
+```
+
+## Smart Delegation
+
+| Task | Agent |
+|------|-------|
+| Directory mapping | `explore` |
+| File analysis | `architect-low` |
+| Content generation | `writer` |
+| Multi-file writes | `executor` |
+
+## Empty Directory Handling
+
+When encountering empty or near-empty directories:
+
+| Condition | Action |
+|-----------|--------|
+| No files, no subdirectories | **Skip** - do not create AGENTS.md |
+| No files, has subdirectories | Create minimal AGENTS.md with subdirectory listing only |
+| Has only generated files (*.min.js, *.map) | Skip or minimal AGENTS.md |
+| Has only config files | Create AGENTS.md describing configuration purpose |
+
+Example minimal AGENTS.md for directory-only containers:
+```markdown
+<!-- Parent: ../AGENTS.md -->
+# {Directory Name}
+
+## Purpose
+Container directory for organizing related modules.
+
+## Subdirectories
+| Directory | Purpose |
+|-----------|---------|
+| `subdir/` | Description (see `subdir/AGENTS.md`) |
+```
+
+## Parallelization Rules
+
+1. **Same-level directories**: Process in parallel
+2. **Different levels**: Sequential (parent first)
+3. **Large directories**: Spawn dedicated agent per directory
+4. **Small directories**: Batch multiple into one agent
+
+## Quality Standards
+
+### Must Include
+- [ ] Accurate file descriptions
+- [ ] Correct parent references
+- [ ] Subdirectory links
+- [ ] AI agent instructions
+
+### Must Avoid
+- [ ] Generic boilerplate
+- [ ] Incorrect file names
+- [ ] Broken parent references
+- [ ] Missing important files
+
+## Example Output
+
+### Root AGENTS.md
+```markdown
+<!-- Generated: 2024-01-15 | Updated: 2024-01-15 -->
+
+# my-project
+
+## Purpose
+A web application for managing user tasks with real-time collaboration features.
+
+## Key Files
+| File | Description |
+|------|-------------|
+| `package.json` | Project dependencies and scripts |
+| `tsconfig.json` | TypeScript configuration |
+| `.env.example` | Environment variable template |
+
+## Subdirectories
+| Directory | Purpose |
+|-----------|---------|
+| `src/` | Application source code (see `src/AGENTS.md`) |
+| `docs/` | Documentation (see `docs/AGENTS.md`) |
+| `tests/` | Test suites (see `tests/AGENTS.md`) |
+
+## For AI Agents
+
+### Working In This Directory
+- Always run `npm install` after modifying package.json
+- Use TypeScript strict mode
+- Follow ESLint rules
+
+### Testing Requirements
+- Run `npm test` before committing
+- Ensure >80% coverage
+
+### Common Patterns
+- Use barrel exports (index.ts)
+- Prefer functional components
+
+## Dependencies
+
+### External
+- React 18.x - UI framework
+- TypeScript 5.x - Type safety
+- Vite - Build tool
+
+<!-- MANUAL: Custom project notes can be added below -->
+```
+
+### Nested AGENTS.md
+```markdown
+<!-- Parent: ../AGENTS.md -->
+<!-- Generated: 2024-01-15 | Updated: 2024-01-15 -->
+
+# components
+
+## Purpose
+Reusable React components organized by feature and complexity.
+
+## Key Files
+| File | Description |
+|------|-------------|
+| `index.ts` | Barrel export for all components |
+| `Button.tsx` | Primary button component |
+| `Modal.tsx` | Modal dialog component |
+
+## Subdirectories
+| Directory | Purpose |
+|-----------|---------|
+| `forms/` | Form-related components (see `forms/AGENTS.md`) |
+| `layout/` | Layout components (see `layout/AGENTS.md`) |
+
+## For AI Agents
+
+### Working In This Directory
+- Each component has its own file
+- Use CSS modules for styling
+- Export via index.ts
+
+### Testing Requirements
+- Unit tests in `__tests__/` subdirectory
+- Use React Testing Library
+
+### Common Patterns
+- Props interfaces defined above component
+- Use forwardRef for DOM-exposing components
+
+## Dependencies
+
+### Internal
+- `src/hooks/` - Custom hooks used by components
+- `src/utils/` - Utility functions
+
+### External
+- `clsx` - Conditional class names
+- `lucide-react` - Icons
+
+<!-- MANUAL: -->
+```
+
+## Triggering Update Mode
+
+When running on an existing codebase with AGENTS.md files:
+
+1. Detect existing files first
+2. Read and parse existing content
+3. Analyze current directory state
+4. Generate diff between existing and current
+5. Apply updates while preserving manual sections
+
+## Performance Considerations
+
+- **Cache directory listings** - Don't re-scan same directories
+- **Batch small directories** - Process multiple at once
+- **Skip unchanged** - If directory hasn't changed, skip regeneration
+- **Parallel writes** - Multiple agents writing different files simultaneously

package/commands/deepsearch.md

@@ -1,3 +1,37 @@
 ---
 description: Thorough codebase search
 ---
+
+# Deep Search Mode
+
+[DEEPSEARCH MODE ACTIVATED]
+
+## Objective
+
+Perform thorough search of the codebase for the specified query, pattern, or concept.
+
+## Search Strategy
+
+1. **Broad Search**
+   - Search for exact matches
+   - Search for related terms and variations
+   - Check common locations (components, utils, services, hooks)
+
+2. **Deep Dive**
+   - Read files with matches
+   - Check imports/exports to find connections
+   - Follow the trail (what imports this? what does this import?)
+
+3. **Synthesize**
+   - Map out where the concept is used
+   - Identify the main implementation
+   - Note related functionality
+
+## Output Format
+
+- **Primary Locations** (main implementations)
+- **Related Files** (dependencies, consumers)
+- **Usage Patterns** (how it's used across the codebase)
+- **Key Insights** (patterns, conventions, gotchas)
+
+Focus on being comprehensive but concise. Cite file paths and line numbers.