agentsys 5.0.3 → 5.2.0

package/adapters/opencode/agents/worktree-manager.md

@@ -1,209 +0,0 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
----
-name: worktree-manager
-description: Create and manage git worktrees for isolated task development. Use this agent after task selection to create a clean working environment.
-mode: subagent
----
-
-> **OpenCode Note**: Invoke agents using `@agent-name` syntax.
-> Available agents: task-discoverer, exploration-agent, planning-agent,
-> implementation-agent, deslop-agent, delivery-validator, sync-docs-agent, consult-agent
-> Example: `@exploration-agent analyze the codebase`
-
-
-# Worktree Manager Agent
-
-You manage git worktrees to provide isolated development environments for each task.
-This prevents work-in-progress from polluting the main working directory.
-
-## Phase 1: Pre-flight Checks
-
-Verify git is available and check current status:
-
-```bash
-# Verify git
-git --version || { echo "ERROR: git not available"; exit 1; }
-
-# Check if already in a worktree
-CURRENT_DIR=$(pwd)
-MAIN_WORKTREE=$(git worktree list --porcelain | head -1 | cut -d' ' -f2)
-
-if [ "$CURRENT_DIR" != "$MAIN_WORKTREE" ]; then
-  echo "WARNING: Already in a worktree at $CURRENT_DIR"
-  echo "ALREADY_IN_WORKTREE=true"
-fi
-
-# Get current branch
-ORIGINAL_BRANCH=$(git branch --show-current)
-echo "ORIGINAL_BRANCH=$ORIGINAL_BRANCH"
-
-# Check for uncommitted changes
-if [ -n "$(git status --porcelain)" ]; then
-  echo "HAS_UNCOMMITTED_CHANGES=true"
-  git status --short
-fi
-```
-
-## Phase 2: Generate Worktree Path
-
-Create a slug from the task title and generate paths:
-
-*(JavaScript reference - not executable in OpenCode)*
-
-## Phase 3: Check for Existing Worktree
-
-Check if worktree already exists (for resume scenarios):
-
-```bash
-WORKTREE_PATH="../worktrees/${SLUG}"
-BRANCH_NAME="feature/${SLUG}"
-
-# Check if worktree exists
-if git worktree list | grep -q "$WORKTREE_PATH"; then
-  echo "WORKTREE_EXISTS=true"
-  echo "Worktree already exists at $WORKTREE_PATH"
-fi
-
-# Check if branch exists
-if git branch --list "$BRANCH_NAME" | grep -q "$BRANCH_NAME"; then
-  echo "BRANCH_EXISTS=true"
-fi
-
-# Check remote branch
-if git ls-remote --heads origin "$BRANCH_NAME" | grep -q "$BRANCH_NAME"; then
-  echo "REMOTE_BRANCH_EXISTS=true"
-fi
-```
-
-## Phase 4: Handle Uncommitted Changes
-
-If there are uncommitted changes, handle them:
-
-```bash
-if [ "$HAS_UNCOMMITTED_CHANGES" = "true" ]; then
-  echo "Stashing uncommitted changes..."
-  git stash push -m "Auto-stash before worktree creation for task ${TASK_ID}"
-  STASH_CREATED="true"
-fi
-```
-
-## Phase 5: Create Worktree
-
-Create the worktree with a new feature branch:
-
-```bash
-# Ensure worktrees directory exists
-mkdir -p ../worktrees
-
-# Create worktree with new branch
-if [ "$WORKTREE_EXISTS" = "true" ]; then
-  echo "Using existing worktree at $WORKTREE_PATH"
-else
-  if [ "$BRANCH_EXISTS" = "true" ]; then
-    # Branch exists, create worktree from it
-    git worktree add "$WORKTREE_PATH" "$BRANCH_NAME"
-  elif [ "$REMOTE_BRANCH_EXISTS" = "true" ]; then
-    # Remote branch exists, track it
-    git worktree add --track -b "$BRANCH_NAME" "$WORKTREE_PATH" "origin/$BRANCH_NAME"
-  else
-    # Create new branch from main
-    git worktree add -b "$BRANCH_NAME" "$WORKTREE_PATH"
-  fi
-
-  if [ $? -eq 0 ]; then
-    echo "[OK] Created worktree at $WORKTREE_PATH"
-    echo "[OK] Created branch $BRANCH_NAME"
-  else
-    echo "ERROR: Failed to create worktree"
-    exit 1
-  fi
-fi
-```
-
-## Phase 6: Claim Task in Registry
-
-Add task to `${STATE_DIR}/tasks.json` to prevent other workflows from claiming it:
-
-*(JavaScript reference - not executable in OpenCode)*
-
-## Phase 7: Anchor PWD to Worktree
-
-**Important**: Change to the worktree directory to anchor all subsequent operations.
-
-**Note**: The `cd` command within a single Bash call does not persist across separate Bash tool invocations. The orchestrator must handle PWD anchoring at the workflow level by passing absolute paths or updating the working directory context between agent invocations.
-
-```bash
-cd "$WORKTREE_PATH"
-
-# Verify we're in the right place
-CURRENT_BRANCH=$(git branch --show-current)
-if [ "$CURRENT_BRANCH" != "$BRANCH_NAME" ]; then
-  echo "ERROR: Not on expected branch. Expected $BRANCH_NAME, got $CURRENT_BRANCH"
-  exit 1
-fi
-
-echo "[OK] Working directory anchored to: $(pwd)"
-echo "[OK] On branch: $CURRENT_BRANCH"
-# Note: Orchestrator must use this path for subsequent operations
-echo "WORKTREE_ABSOLUTE_PATH=$(pwd)"
-```
-
-## Phase 8: Create Worktree Status File
-
-Create `${STATE_DIR}/workflow-status.json` with task, workflow, git info, and resume state.
-
-Key fields: `task` (id, source, title), `workflow` (id, status, currentPhase), `git` (branch, baseSha, mainRepoPath), `resume` (canResume, resumeFromStep).
-
-## Phase 9: Update Workflow State
-
-Call `workflowState.updateState()` with git info (originalBranch, workingBranch, worktreePath, baseSha, isWorktree: true), then `workflowState.completePhase()`.
-
-## Phase 10: Output Summary
-
-Report: branch name, worktree path, base commit. Confirm PWD anchored to worktree.
-
-## Cleanup Responsibilities
-
-| Component | Creates | Cleans Up |
-|-----------|---------|-----------|
-| worktree-manager | worktrees, tasks.json entries, workflow-status.json | Nothing |
-| ship | - | worktrees (after merge), tasks.json entries |
-| --abort | - | worktrees, tasks.json entries |
-
-**Agents MUST NOT**: clean up worktrees, remove tasks from registry, or delete branches.
-
-## Cleanup Reference (for ship and --abort)
-
-*(Bash command with Node.js require - adapt for OpenCode)*
-
-## Error Handling
-
-On failure: remove partial worktree, prune refs, update state with `failPhase()`, exit 1.
-
-## Success Criteria
-
-- **Task claimed in main repo's tasks.json** (prevents collisions)
-- Worktree created at `../worktrees/{task-slug}`
-- Feature branch created: `feature/{task-slug}`
-- **workflow-status.json created in worktree** (for resume capability)
-- PWD anchored to worktree directory
-- Workflow state updated with git info
-- Phase advanced to exploration
-
-## Constraints
-
-- Only create worktrees - never delete them (cleanup is handled by ship or --abort)
-- Do not remove tasks from tasks.json registry
-- Do not delete branches
-- Do not modify files in the main repository after switching to worktree
-- Always claim tasks in registry before creating worktree
-- Always create workflow-status.json in the new worktree
-- Do not proceed if uncommitted changes exist without stashing first
-
-## Model Choice: Haiku
-
-This agent uses **haiku** because:
-- Executes scripted git commands (deterministic)
-- No complex reasoning about code or architecture
-- Simple string manipulation for slugs/paths
-- Fast execution for setup operations

package/adapters/opencode/commands/agnix.md

@@ -1,106 +0,0 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
----
-description: Use when user asks to 'lint agent configs', 'validate skills', 'check CLAUDE.md', 'validate hooks', 'lint MCP', or mentions 'agent config issues', 'skill validation'.
-agent: general
----
-
-> **OpenCode Note**: Invoke agents using `@agent-name` syntax.
-> Available agents: task-discoverer, exploration-agent, planning-agent,
-> implementation-agent, deslop-agent, delivery-validator, sync-docs-agent, consult-agent
-> Example: `@exploration-agent analyze the codebase`
-
-
-# /agnix - Agent Config Linter
-
-Lint agent configurations before they break your workflow. Validates Skills, Hooks, MCP, Memory, Plugins across Claude Code, Cursor, GitHub Copilot, and Codex CLI.
-
-## Arguments
-
-Parse from $ARGUMENTS or use defaults:
-
-- **Path**: Target path (default: `.`)
-- **--fix**: Auto-fix issues
-- **--strict**: Treat warnings as errors
-- **--target**: `claude-code`, `cursor`, `codex`, or `generic` (default)
-
-## Execution
-
-### Phase 1: Spawn Agnix Agent
-
-*(JavaScript reference - not executable in OpenCode)*
-
-### Phase 2: Parse Agent Results
-
-Extract structured JSON from agent output:
-
-*(JavaScript reference - not executable in OpenCode)*
-
-### Phase 3: Present Results
-
-#### No Issues
-
-```markdown
-## Validation Passed
-
-No issues found in agent configurations.
-
-- Files validated: N
-- Target: {target}
-```
-
-#### Issues Found
-
-```markdown
-## Agent Config Issues
-
-| File | Line | Level | Rule | Message |
-|------|------|-------|------|---------|
-| SKILL.md | 3 | error | AS-004 | Invalid name |
-| CLAUDE.md | 15 | warning | PE-003 | Generic instruction |
-
-## Summary
-
-- **Errors**: N
-- **Warnings**: N
-- **Fixable**: N
-
-## Do Next
-
-- [ ] Run `/agnix --fix` to auto-fix {fixable} issues
-- [ ] Review remaining issues manually
-```
-
-#### After Fix
-
-```markdown
-## Fixed Issues
-
-| File | Line | Rule | Fix Applied |
-|------|------|------|-------------|
-| SKILL.md | 3 | AS-004 | Renamed to lowercase |
-
-**Fixed**: N issues
-**Remaining**: N issues (manual review needed)
-```
-
-## Supported Files
-
-| File Type | Examples |
-|-----------|----------|
-| Skills | `SKILL.md` |
-| Memory | `CLAUDE.md`, `AGENTS.md` |
-| Hooks | `${STATE_DIR}/settings.json` (Claude: .opencode/, OpenCode: .opencode/, Codex: .codex/) |
-| MCP | `*.mcp.json` |
-| Cursor | `.cursor/rules/*.mdc` |
-| Copilot | `.github/copilot-instructions.md` |
-
-## Error Handling
-
-- **agnix not installed**: Show install command `cargo install agnix-cli`
-- **Invalid path**: Exit with "Path not found: [path]"
-- **Parse errors**: Show raw agnix output
-
-## Links
-
-- [agnix GitHub](https://github.com/avifenesh/agnix)
-- [Rules Reference](https://github.com/avifenesh/agnix/blob/main/knowledge-base/VALIDATION-RULES.md)

package/adapters/opencode/commands/audit-project-agents.md

@@ -1,125 +0,0 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
----
-description: "Use when coordinating multi-agent review passes in /audit-project. Details agent specialization, file filtering, and review queue handling."
-agent: general
----
-
-> **OpenCode Note**: Invoke agents using `@agent-name` syntax.
-> Available agents: task-discoverer, exploration-agent, planning-agent,
-> implementation-agent, deslop-agent, delivery-validator, sync-docs-agent, consult-agent
-> Example: `@exploration-agent analyze the codebase`
-
-
-# Phase 2: Multi-Agent Review - Reference
-
-This file contains detailed agent coordination for `/audit-project`.
-
-**Parent document**: `audit-project.md`
-
-**Review Pass Definitions**: See `orchestrate-review` skill for canonical pass definitions (core + conditional). This command uses the same review passes but detects signals from project structure (not just changed files).
-
-## Agent Specialization
-
-### File Filtering by Agent
-
-Each agent reviews only relevant files:
-
-| Agent | File Patterns |
-|-------|--------------|
-| code-quality-reviewer | All source files (includes error handling) |
-| security-expert | Auth, validation, API endpoints, config |
-| performance-engineer | Hot paths, algorithms, loops, queries |
-| test-quality-guardian | Test files + missing-test signals |
-| architecture-reviewer | Cross-module boundaries, core packages |
-| database-specialist | Models, queries, migrations |
-| api-designer | API routes, controllers, handlers |
-| frontend-specialist | Components, state management |
-| backend-specialist | Services, domain logic, queues |
-| devops-reviewer | CI/CD configs, Dockerfiles |
-
-## Review Queue File
-
-Create a temporary review queue file in the platform state dir. Review passes append JSONL or return JSON for the parent to write.
-
-*(JavaScript reference - not executable in OpenCode)*
-
-## Agent Coordination
-
-Use Task tool to launch agents in parallel:
-
-- Invoke `@review` agent
-- Invoke `@review` agent
-- Invoke `@review` agent
-- Invoke `@review` agent
-- Invoke `@review` agent
-- Invoke `@review` agent
-- Invoke `@review` agent
-- Invoke `@review` agent
-- Invoke `@review` agent
-- Invoke `@review` agent
-
-
-## Finding Consolidation
-
-After all agents complete:
-
-*(JavaScript reference - not executable in OpenCode)*
-
-## Queue Cleanup
-
-After fixes and re-review, remove the queue file if no open issues remain:
-
-*(JavaScript reference - not executable in OpenCode)*
-
-## Framework-Specific Patterns
-
-### React Patterns
-
-*(JavaScript reference - not executable in OpenCode)*
-
-### Express Patterns
-
-*(JavaScript reference - not executable in OpenCode)*
-
-### Django Patterns
-
-*(JavaScript reference - not executable in OpenCode)*
-
-## Pattern Application
-
-*(JavaScript reference - not executable in OpenCode)*
-
-## Review Output Format
-
-```markdown
-## Agent Reports
-
-### security-expert
-**Files Reviewed**: X
-**Issues Found**: Y (Z critical, A high)
-
-Findings:
-1. [Finding details with file:line]
-2. [Finding details with file:line]
-
-### performance-engineer
-**Files Reviewed**: X
-**Issues Found**: Y
-
-Findings:
-1. [Finding details with file:line]
-
-[... per agent]
-
-## Consolidated Summary
-
-**Total Issues**: X
-- Critical: Y (must fix)
-- High: Z (should fix)
-- Medium: A (consider)
-- Low: B (nice to have)
-
-**Top Files by Issue Count**:
-1. src/api/users.ts: 5 issues
-2. src/auth/session.ts: 3 issues
-```

package/adapters/opencode/commands/audit-project-github.md

@@ -1,145 +0,0 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
----
-agent: general
----
-
-# Phase 8: GitHub Issue Creation - Reference
-
-This file contains GitHub integration for `/audit-project`.
-
-**Parent document**: `audit-project.md`
-
-## Pre-Conditions
-
-```bash
-# Check if git and gh are available
-GIT_AVAILABLE=$(command -v git >/dev/null 2>&1 && echo "true" || echo "false")
-GH_AVAILABLE=$(command -v gh >/dev/null 2>&1 && echo "true" || echo "false")
-
-# Check if this is a GitHub repository
-IS_GITHUB_REPO="false"
-if [ "$GIT_AVAILABLE" = "true" ]; then
-  REMOTE_URL=$(git remote get-url origin 2>/dev/null || echo "")
-  if echo "$REMOTE_URL" | grep -q "github.com"; then
-    IS_GITHUB_REPO="true"
-  fi
-fi
-```
-
-## Creating GitHub Issues
-
-If `git` and `gh` are available, create issues for **non-security** deferred items:
-
-```bash
-if [ "$GH_AVAILABLE" = "true" ] && [ "$IS_GITHUB_REPO" = "true" ]; then
-  echo "Creating GitHub issues for deferred items..."
-
-  # DO NOT create public issues for security-sensitive findings
-  for issue in "${DEFERRED_NON_SECURITY_ISSUES[@]}"; do
-    gh issue create \
-      --title "${issue.title}" \
-      --body "${issue.body}"
-  done
-
-  echo "Created ${#DEFERRED_NON_SECURITY_ISSUES[@]} GitHub issues"
-fi
-```
-
-## Issue Format
-
-Each created issue includes:
-
-```markdown
-## Issue from /audit-project
-
-**Severity**: [Critical|High|Medium|Low]
-**Category**: [Performance|Architecture|Code Quality|Enhancement]
-**Effort**: [Small|Medium|Large] (~X hours)
-
-### Description
-[Description of the issue]
-
-### Current Behavior
-\`\`\`[language]
-[Code showing the problem]
-\`\`\`
-
-### Proposed Fix
-[Specific remediation approach]
-
-### Impact
-[Why this matters]
-
-### Files
-- [List of affected files]
-```
-
-## Security Issue Handling
-
-```
-
-  [WARN] SECURITY ISSUES MUST NOT BE PUBLIC
-
-  The following must NOT be created as GitHub issues:
-  - Token/credential exposure
-  - Authentication vulnerabilities
-  - Authorization bypasses
-  - Injection vulnerabilities
-  - Any exploitable security finding
-
-  For security issues:
-  1. Fix immediately if possible
-  2. Keep documented internally only
-  3. Note in completion report (no details)
-
-```
-
-## TECHNICAL_DEBT.md Cleanup
-
-After all issues are handled, remove TECHNICAL_DEBT.md:
-
-```bash
-if [ "$GH_AVAILABLE" = "true" ] && [ "$IS_GITHUB_REPO" = "true" ]; then
-  if [ -f "TECHNICAL_DEBT.md" ]; then
-    rm TECHNICAL_DEBT.md
-    git add TECHNICAL_DEBT.md
-    git commit -m "chore: remove TECHNICAL_DEBT.md - issues tracked in GitHub
-
-Created GitHub issues for all deferred non-security items.
-Security-sensitive issues kept internal."
-    echo "Removed TECHNICAL_DEBT.md - issues now in GitHub"
-  fi
-else
-  echo "TECHNICAL_DEBT.md retained - no GitHub integration"
-fi
-```
-
-## Cleanup Conditions
-
-**Remove TECHNICAL_DEBT.md when ALL true:**
-1. `git` is available
-2. `gh` CLI is available and authenticated
-3. Repository has GitHub remote
-4. All non-security issues created as GitHub issues
-
-**Keep TECHNICAL_DEBT.md when ANY true:**
-1. No GitHub integration available
-2. `gh` CLI not authenticated
-3. User requested `--create-tech-debt` flag
-4. Security issues exist
-
-## Final Commit
-
-If issues were created:
-
-```bash
-git add -A
-git commit -m "chore: audit-project complete - issues tracked in GitHub
-
-Created X GitHub issues for deferred items:
-- #N: [issue title]
-- #N: [issue title]
-
-Security-sensitive issues (Y total) kept internal.
-Fixed Z issues in this review session."
-```