aidevops 2.52.1 → 2.53.2

package/.agent/scripts/commands/code-simplifier.md

@@ -1,86 +0,0 @@
----
-description: Simplify and refine code for clarity, consistency, and maintainability
-agent: Build+
-mode: subagent
----
-
-Simplify and refine code for clarity, consistency, and maintainability while preserving all functionality.
-
-Target: $ARGUMENTS
-
-## Quick Reference
-
-- **Purpose**: Simplify code without changing functionality
-- **Priority**: Clarity over brevity
-- **Scope**: Recently modified code unless target specified
-
-## Process
-
-1. **Identify scope**: Use $ARGUMENTS if provided, otherwise find recently modified files
-2. **Read the code-simplifier agent**: `tools/code-review/code-simplifier.md`
-3. **Apply refinements** following the agent's principles
-4. **Verify** functionality is preserved
-5. **Report** changes made
-
-## Scope Detection
-
-If no target specified ($ARGUMENTS is empty):
-
-```bash
-# Find recently modified files (last commit or staged)
-git diff --name-only HEAD~1
-git diff --name-only --staged
-```
-
-If target specified:
-- Directory path: Simplify all code files in directory
-- File path: Simplify specific file
-- `--all`: Review entire codebase (use sparingly)
-
-## Refinement Principles
-
-From `tools/code-review/code-simplifier.md`:
-
-1. **Preserve Functionality**: Never change what code does
-2. **Apply Project Standards**: Follow CLAUDE.md/AGENTS.md conventions
-3. **Enhance Clarity**: Reduce complexity, eliminate redundancy
-4. **Maintain Balance**: Avoid over-simplification
-5. **Focus Scope**: Only refine recently modified code unless instructed otherwise
-
-## Key Patterns to Fix
-
-- Nested ternaries -> switch/if-else chains
-- Dense one-liners -> readable multi-line
-- Redundant abstractions -> direct code
-- Obvious comments -> remove
-- Inconsistent naming -> standardize
-
-## Output Format
-
-```text
-Code Simplification Report
-==========================
-
-Files reviewed: {count}
-Changes made: {count}
-
-{file1}:
-  - Line {n}: {before} -> {after}
-  - Line {m}: Removed redundant {description}
-
-{file2}:
-  - Line {n}: Simplified nested ternary to if/else
-
-Functionality: Preserved
-```
-
-## Integration
-
-After simplification, suggest:
-
-```text
-Next steps:
-1. Run /linters-local to validate
-2. Review changes with git diff
-3. Commit if satisfied
-```

package/.agent/scripts/commands/full-loop.md

@@ -1,246 +0,0 @@
----
-description: Start end-to-end development loop (task → preflight → PR → postflight → deploy)
-agent: Build+
-mode: subagent
----
-
-Start a full development loop that chains all phases from task implementation to deployment.
-
-Task/Prompt: $ARGUMENTS
-
-## Full Loop Phases
-
-```text
-Task Development → Preflight → PR Create → PR Review → Postflight → Deploy
-```
-
-## Workflow
-
-### Step 1: Auto-Branch Setup
-
-The loop automatically handles branch setup when on main/master:
-
-```bash
-# Run pre-edit check in loop mode with task description
-~/.aidevops/agents/scripts/pre-edit-check.sh --loop-mode --task "$ARGUMENTS"
-```
-
-**Exit codes:**
-- `0` - Already on feature branch OR docs-only task (proceed)
-- `1` - Interactive mode fallback (shouldn't happen in loop)
-- `2` - Code task on main (auto-create worktree)
-
-**Auto-decision logic:**
-- **Docs-only tasks** (README, CHANGELOG, docs/, typos): Stay on main
-- **Code tasks** (features, fixes, refactors, enhancements): Auto-create worktree
-
-**Detection keywords:**
-- Docs-only: `readme`, `changelog`, `documentation`, `docs/`, `typo`, `spelling`
-- Code (overrides docs): `feature`, `fix`, `bug`, `implement`, `refactor`, `add`, `update`, `enhance`, `port`, `ssl`
-
-**When worktree is needed:**
-
-```bash
-# Generate branch name from task (sanitized, truncated to 40 chars)
-branch_name=$(echo "$ARGUMENTS" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | cut -c1-40)
-~/.aidevops/agents/scripts/worktree-helper.sh add "feature/$branch_name"
-# Continue in new worktree directory
-```
-
-Also verify:
-- **Clean working directory**: Uncommitted changes should be committed or stashed
-- **Git remote configured**: Need to push and create PR
-
-```bash
-git status --short
-```
-
-### Step 2: Start Full Loop
-
-```bash
-~/.aidevops/agents/scripts/full-loop-helper.sh start "$ARGUMENTS"
-```
-
-This will:
-1. Initialize the Ralph loop for task development
-2. Set up state tracking in `.agent/loop-state/full-loop.local.md`
-3. Begin iterating on the task
-
-### Step 3: Task Development (Ralph Loop)
-
-The AI will iterate on the task until outputting:
-
-```text
-<promise>TASK_COMPLETE</promise>
-```
-
-**Completion criteria:**
-- All requirements implemented
-- Tests passing (if applicable)
-- Code quality acceptable
-- README.md updated (if adding features/APIs)
-- Conventional commits used (for auto-changelog)
-
-### Step 4: Automatic Phase Progression
-
-After task completion, the loop automatically:
-
-1. **Preflight**: Runs quality checks, auto-fixes issues
-2. **PR Create**: Creates pull request with `gh pr create --fill`
-3. **PR Review**: Monitors CI checks and review status
-4. **Postflight**: Verifies release health after merge
-5. **Deploy**: Runs `setup.sh` (aidevops repos only)
-
-### Step 5: Human Decision Points
-
-The loop pauses for human input at:
-
-| Point | When | Action Required |
-|-------|------|-----------------|
-| Merge approval | If repo requires human approval | Approve PR in GitHub |
-| Rollback | If postflight detects issues | Decide whether to rollback |
-| Scope change | If task evolves beyond original | Confirm new scope |
-
-### Step 6: Completion
-
-When all phases complete:
-
-```text
-<promise>FULL_LOOP_COMPLETE</promise>
-```
-
-## Commands
-
-```bash
-# Start new loop
-/full-loop "Implement feature X with tests"
-
-# Check status
-~/.aidevops/agents/scripts/full-loop-helper.sh status
-
-# Resume after interruption
-~/.aidevops/agents/scripts/full-loop-helper.sh resume
-
-# Cancel loop
-~/.aidevops/agents/scripts/full-loop-helper.sh cancel
-```
-
-## Options
-
-Pass options after the prompt:
-
-```bash
-/full-loop "Fix bug Y" --max-task-iterations 30 --skip-postflight
-```
-
-| Option | Description |
-|--------|-------------|
-| `--max-task-iterations N` | Max iterations for task (default: 50) |
-| `--max-preflight-iterations N` | Max iterations for preflight (default: 5) |
-| `--max-pr-iterations N` | Max iterations for PR review (default: 20) |
-| `--skip-preflight` | Skip preflight checks |
-| `--skip-postflight` | Skip postflight monitoring |
-| `--no-auto-pr` | Pause for manual PR creation |
-| `--no-auto-deploy` | Don't auto-run setup.sh |
-
-## Examples
-
-```bash
-# Basic feature implementation
-/full-loop "Add user authentication with JWT tokens"
-
-# Bug fix with limited iterations
-/full-loop "Fix memory leak in connection pool" --max-task-iterations 20
-
-# Skip postflight for quick iteration
-/full-loop "Update documentation" --skip-postflight
-
-# Manual PR creation
-/full-loop "Refactor database layer" --no-auto-pr
-```
-
-## Documentation & Changelog
-
-### README Updates
-
-When implementing features or APIs, include README updates in your task:
-
-```bash
-/full-loop "Add user authentication with JWT tokens and update README"
-```
-
-The task development phase should update README.md with:
-- New feature documentation
-- Usage examples
-- API endpoint descriptions
-- Configuration options
-
-### Changelog (Auto-Generated)
-
-The release workflow auto-generates CHANGELOG.md from conventional commits. Use proper commit prefixes during task development:
-
-| Prefix | Changelog Section | Example |
-|--------|-------------------|---------|
-| `feat:` | Added | `feat: add JWT authentication` |
-| `fix:` | Fixed | `fix: resolve token expiration bug` |
-| `docs:` | Changed | `docs: update API documentation` |
-| `perf:` | Changed | `perf: optimize database queries` |
-| `refactor:` | Changed | `refactor: simplify auth middleware` |
-| `chore:` | (excluded) | `chore: update dependencies` |
-
-See `workflows/changelog.md` for format details.
-
-## OpenProse Orchestration
-
-For complex multi-phase workflows, consider expressing the full loop in OpenProse DSL:
-
-```prose
-agent developer:
-  model: opus
-  prompt: "You are a senior developer"
-
-# Phase 1: Task Development
-loop until **task is complete** (max: 50):
-  session: developer
-    prompt: "Implement the feature, run tests, fix issues"
-
-# Phase 2: Preflight (parallel quality checks)
-parallel:
-  lint = session "Run linters and fix issues"
-  types = session "Check types and fix issues"
-  tests = session "Run tests and fix failures"
-
-if **any checks failed**:
-  loop until **all checks pass** (max: 5):
-    session "Fix remaining issues"
-      context: { lint, types, tests }
-
-# Phase 3: PR Creation
-let pr = session "Create pull request with gh pr create --fill"
-
-# Phase 4: PR Review Loop
-loop until **PR is merged** (max: 20):
-  parallel:
-    ci = session "Check CI status"
-    review = session "Check review status"
-  
-  if **CI failed**:
-    session "Fix CI issues and push"
-  
-  if **changes requested**:
-    session "Address review feedback and push"
-
-# Phase 5: Postflight
-session "Verify release health"
-```
-
-See `tools/ai-orchestration/openprose.md` for full OpenProse documentation.
-
-## Related
-
-- `workflows/ralph-loop.md` - Ralph loop technique details
-- `workflows/preflight.md` - Pre-commit quality checks
-- `workflows/pr.md` - PR creation workflow
-- `workflows/postflight.md` - Post-release verification
-- `workflows/changelog.md` - Changelog format and validation
-- `tools/ai-orchestration/openprose.md` - OpenProse DSL for multi-agent orchestration

package/.agent/scripts/commands/postflight-loop.md

@@ -1,103 +0,0 @@
----
-description: Monitor release health for a specified duration
-agent: Build+
-mode: subagent
----
-
-Monitor release health after deployment using iterative checks.
-
-Arguments: $ARGUMENTS
-
-## Usage
-
-```bash
-/postflight-loop [--monitor-duration Nm] [--max-iterations N]
-```
-
-## Options
-
-| Option | Description | Default |
-|--------|-------------|---------|
-| `--monitor-duration <t>` | How long to monitor (e.g., 5m, 10m, 1h) | 5m |
-| `--max-iterations <n>` | Max checks during monitoring | 5 |
-
-## Workflow
-
-### Step 1: Parse Arguments
-
-Extract from $ARGUMENTS:
-- `monitor_duration` - Duration string (e.g., "10m", "1h")
-- `max_iterations` - Number of check iterations
-
-### Step 2: Run Postflight Loop
-
-Execute the quality loop helper:
-
-```bash
-~/.aidevops/agents/scripts/quality-loop-helper.sh postflight $ARGUMENTS
-```
-
-### Step 3: Report Results
-
-The script performs these checks each iteration:
-
-1. **CI Workflow Status** - Latest GitHub Actions workflow state
-2. **Release Tag Exists** - Verify the release tag was created
-3. **Version Consistency** - VERSION file matches release tag
-
-## Completion Promise
-
-When all checks pass: `<promise>RELEASE_HEALTHY</promise>`
-
-## Examples
-
-**Monitor for 10 minutes:**
-
-```bash
-/postflight-loop --monitor-duration 10m
-```
-
-**Extended monitoring with more checks:**
-
-```bash
-/postflight-loop --monitor-duration 1h --max-iterations 10
-```
-
-**Quick verification:**
-
-```bash
-/postflight-loop --monitor-duration 2m --max-iterations 3
-```
-
-## State Tracking
-
-Progress is tracked in `.agent/loop-state/quality-loop.local.md`:
-
-```markdown
-## Postflight Loop State
-
-- **Status:** monitoring
-- **Iteration:** 3/5
-- **Elapsed:** 180s/600s
-- **Last Check:** 2025-01-11T14:30:00Z
-
-### Check Results
-- [x] CI workflow: passing
-- [x] Release tag: v2.44.0 exists
-- [x] Version consistency: matched
-```
-
-## When to Use
-
-- After running `/release` to verify deployment health
-- After manual releases to confirm everything is working
-- As part of CI/CD pipeline verification
-
-## Related Commands
-
-| Command | Purpose |
-|---------|---------|
-| `/preflight` | Quality checks before release |
-| `/release` | Full release workflow |
-| `/postflight` | Single postflight check (no loop) |
-| `/preflight-loop` | Iterative preflight until passing |

package/.agent/scripts/commands/recall.md

@@ -1,182 +0,0 @@
----
-description: Search and retrieve memories from previous sessions
-agent: Build+
-mode: subagent
----
-
-Search stored memories for relevant knowledge.
-
-Search query: $ARGUMENTS
-
-## Workflow
-
-### Step 1: Search Memories
-
-Run the search:
-
-```bash
-~/.aidevops/agents/scripts/memory-helper.sh recall "{query}"
-```
-
-### Step 2: Present Results
-
-If results found:
-
-```text
-Found {count} memories for "{query}":
-
-1. [{type}] {content}
-   Tags: {tags} | Project: {project} | {age}
-   
-2. [{type}] {content}
-   Tags: {tags} | Project: {project} | {age}
-
----
-Actions:
-- Use memory #1 in current context
-- Search with different terms
-- Show more results
-```
-
-If no results:
-
-```text
-No memories found for "{query}"
-
-Try:
-- Different keywords
-- Broader search terms
-- /recall --recent (show latest memories)
-```
-
-### Step 3: Apply Memory
-
-When user selects a memory, incorporate it into the current context:
-
-```text
-Applying memory: "{content}"
-
-This suggests: {interpretation for current task}
-```
-
-## Search Options
-
-| Command | Purpose |
-|---------|---------|
-| `/recall {query}` | Search by keywords |
-| `/recall --type WORKING_SOLUTION` | Filter by type |
-| `/recall --project myapp` | Filter by project |
-| `/recall --recent` | Show 10 most recent |
-| `/recall --stats` | Show memory statistics |
-
-## Examples
-
-**Basic search:**
-
-```text
-User: /recall cors
-AI: Found 2 memories for "cors":
-
-    1. [WORKING_SOLUTION] Fixed CORS by adding Access-Control-Allow-Origin header to nginx.conf
-       Tags: cors,nginx,headers | Project: api-gateway | 3 days ago
-       
-    2. [FAILED_APPROACH] Setting CORS in Express middleware didn't work with nginx proxy
-       Tags: cors,express,nginx | Project: api-gateway | 3 days ago
-
-    Which memory is relevant to your current task?
-```
-
-**Type-filtered search:**
-
-```text
-User: /recall --type USER_PREFERENCE
-AI: Found 5 user preferences:
-
-    1. [USER_PREFERENCE] Use conventional commit format
-       Tags: git,commits | Global | 1 week ago
-       
-    2. [USER_PREFERENCE] Prefer tabs over spaces (width: 2)
-       Tags: formatting,style | Global | 2 weeks ago
-    ...
-```
-
-**Project-specific search:**
-
-```text
-User: /recall --project wordpress-plugin
-AI: Found 8 memories for project "wordpress-plugin":
-
-    1. [CODEBASE_PATTERN] All hooks use prefix 'myplugin_'
-    2. [DECISION] Using SCF instead of ACF for custom fields
-    3. [WORKING_SOLUTION] Fixed activation hook by checking PHP version first
-    ...
-```
-
-**Recent memories:**
-
-```text
-User: /recall --recent
-AI: 10 most recent memories:
-
-    1. [WORKING_SOLUTION] Memory system uses SQLite FTS5 (today)
-    2. [DECISION] Chose SQLite over Postgres for zero dependencies (today)
-    3. [TOOL_CONFIG] ShellCheck requires local var pattern (yesterday)
-    ...
-```
-
-## Memory Statistics
-
-```text
-User: /recall --stats
-AI: Memory Statistics:
-    
-    Total entries: 47
-    By type:
-      WORKING_SOLUTION: 15
-      CODEBASE_PATTERN: 12
-      USER_PREFERENCE: 8
-      FAILED_APPROACH: 6
-      DECISION: 4
-      TOOL_CONFIG: 2
-    
-    By project:
-      global: 20
-      api-gateway: 12
-      wordpress-plugin: 8
-      aidevops: 7
-    
-    Oldest: 45 days ago
-    Most accessed: "conventional commits" (12 accesses)
-```
-
-## Proactive Recall
-
-AI assistants should proactively search memories when:
-
-1. Starting work on a project (check project-specific memories)
-2. Encountering an error (search for similar issues)
-3. Making architecture decisions (check past decisions)
-4. Setting up tools (check TOOL_CONFIG memories)
-
-```text
-AI: Before we start, let me check for relevant memories...
-    [Searches: /recall --project {current-project}]
-    
-    Found 3 relevant memories:
-    - This project uses conventional commits
-    - API routes follow /api/v1/{resource} pattern
-    - Tests require DATABASE_URL env var
-```
-
-## Memory Maintenance
-
-Memories track access patterns. Stale memories (>90 days, never accessed) can be pruned:
-
-```bash
-# Validate memory health
-~/.aidevops/agents/scripts/memory-helper.sh validate
-
-# Prune stale entries (dry-run first)
-~/.aidevops/agents/scripts/memory-helper.sh prune --dry-run
-~/.aidevops/agents/scripts/memory-helper.sh prune
-```