agentsys 5.1.0 → 5.2.1

package/adapters/opencode/commands/delivery-approval.md

@@ -1,211 +0,0 @@
----
-description: Validate task completion and approve for shipping. Can be used standalone or called by the workflow. Runs autonomous validation checks.
-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`
-
-
-# /delivery-approval - Delivery Validation
-
-Validate that the current work is complete and ready to ship.
-This command runs the same validation as the workflow's delivery-validator agent.
-
-## Arguments
-
-- `--task-id ID`: Specify task ID to validate against (default: from workflow state)
-- `--verbose`: Show detailed output for each check
-
-## Parse Arguments
-
-*(JavaScript reference - not executable in OpenCode)*
-
-## Phase 1: Get Context
-
-*(JavaScript reference - not executable in OpenCode)*
-
-## Phase 2: Run Validation Checks
-
-### Check 1: Git State
-
-```bash
-# Check for uncommitted changes
-UNCOMMITTED=$(git status --porcelain)
-if [ -n "$UNCOMMITTED" ]; then
-  echo "UNCOMMITTED_CHANGES=true"
-  echo "$UNCOMMITTED"
-fi
-
-# Check if ahead of remote
-AHEAD=$(git rev-list --count origin/main..HEAD)
-echo "COMMITS_AHEAD=$AHEAD"
-
-# Check branch name
-BRANCH=$(git branch --show-current)
-echo "BRANCH=$BRANCH"
-```
-
-### Check 2: Tests Pass
-
-```bash
-# Detect and run tests
-if [ -f "package.json" ]; then
-  if grep -q '"test"' package.json; then
-    echo "Running npm test..."
-    npm test 2>&1
-    TEST_RESULT=$?
-    echo "TEST_RESULT=$TEST_RESULT"
-  else
-    echo "NO_TEST_SCRIPT=true"
-  fi
-elif [ -f "pytest.ini" ] || [ -f "pyproject.toml" ]; then
-  echo "Running pytest..."
-  pytest -v 2>&1
-  TEST_RESULT=$?
-  echo "TEST_RESULT=$TEST_RESULT"
-elif [ -f "Cargo.toml" ]; then
-  echo "Running cargo test..."
-  cargo test 2>&1
-  TEST_RESULT=$?
-  echo "TEST_RESULT=$TEST_RESULT"
-elif [ -f "go.mod" ]; then
-  echo "Running go test..."
-  go test ./... -v 2>&1
-  TEST_RESULT=$?
-  echo "TEST_RESULT=$TEST_RESULT"
-fi
-```
-
-### Check 3: Build Passes
-
-```bash
-# Detect and run build
-if [ -f "package.json" ] && grep -q '"build"' package.json; then
-  echo "Running npm run build..."
-  npm run build 2>&1
-  BUILD_RESULT=$?
-  echo "BUILD_RESULT=$BUILD_RESULT"
-elif [ -f "Cargo.toml" ]; then
-  echo "Running cargo build..."
-  cargo build --release 2>&1
-  BUILD_RESULT=$?
-  echo "BUILD_RESULT=$BUILD_RESULT"
-elif [ -f "go.mod" ]; then
-  echo "Running go build..."
-  go build ./... 2>&1
-  BUILD_RESULT=$?
-  echo "BUILD_RESULT=$BUILD_RESULT"
-else
-  echo "NO_BUILD_SCRIPT=true"
-  BUILD_RESULT=0
-fi
-```
-
-### Check 4: Lint Passes
-
-```bash
-# Run linter if available
-if [ -f "package.json" ] && grep -q '"lint"' package.json; then
-  echo "Running npm run lint..."
-  npm run lint 2>&1
-  LINT_RESULT=$?
-  echo "LINT_RESULT=$LINT_RESULT"
-elif [ -f ".eslintrc.js" ] || [ -f ".eslintrc.json" ]; then
-  echo "Running eslint..."
-  npx eslint . 2>&1
-  LINT_RESULT=$?
-  echo "LINT_RESULT=$LINT_RESULT"
-else
-  echo "NO_LINTER=true"
-  LINT_RESULT=0
-fi
-```
-
-### Check 5: Type Check (TypeScript)
-
-```bash
-if [ -f "tsconfig.json" ]; then
-  echo "Running tsc --noEmit..."
-  npx tsc --noEmit 2>&1
-  TYPE_RESULT=$?
-  echo "TYPE_RESULT=$TYPE_RESULT"
-else
-  echo "NO_TYPESCRIPT=true"
-  TYPE_RESULT=0
-fi
-```
-
-## Phase 3: Check Task Requirements
-
-*(JavaScript reference - not executable in OpenCode)*
-
-## Phase 4: Aggregate Results
-
-*(JavaScript reference - not executable in OpenCode)*
-
-## Phase 5: Output Results
-
-### Summary Report
-
-*(JavaScript reference - not executable in OpenCode)*
-
-### JSON Output (for scripting)
-
-```json
-{
-  "approved": ${allPassed},
-  "task": {
-    "id": "${task?.id || 'N/A'}",
-    "title": "${task?.title || 'N/A'}"
-  },
-  "checks": {
-    "gitState": ${JSON.stringify(checks.gitState)},
-    "tests": ${JSON.stringify(checks.tests)},
-    "build": ${JSON.stringify(checks.build)},
-    "lint": ${JSON.stringify(checks.lint)},
-    "typeCheck": ${JSON.stringify(checks.typeCheck)},
-    "requirements": ${JSON.stringify(checks.requirements)}
-  },
-  "failedChecks": ${JSON.stringify(failedChecks)},
-  "summary": "${allPassed ? 'All checks passed' : `Failed: ${failedChecks.join(', ')}`}"
-}
-```
-
-## Examples
-
-```bash
-# Basic validation
-/delivery-approval
-
-# With verbose output
-/delivery-approval --verbose
-
-# For specific task
-/delivery-approval --task-id 142
-
-# Combined
-/delivery-approval --task-id 142 --verbose
-```
-
-## Integration with Workflow
-
-When called from the next-task workflow:
-1. Task context is read from workflow state
-2. Results are written back to workflow state
-3. Workflow continues to ship phase if approved
-
-When called standalone:
-1. Attempts to infer task from commits
-2. Runs all validation checks
-3. Reports results but doesn't modify workflow state
-
-## Success Criteria
-
-- Runs all validation checks (tests, build, lint, types)
-- Checks task requirements if available
-- Provides clear pass/fail determination
-- Shows actionable fixes for failures
-- Works both standalone and in workflow context

package/adapters/opencode/commands/deslop.md

@@ -1,131 +0,0 @@
----
-description: This skill should be used when the user asks to "clean up slop", "remove AI artifacts", "deslop the codebase", "find debug statements", "remove console.logs", "repo hygiene", or mentions "AI slop", "code cleanup", "slop detection".
-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`
-
-
-# /deslop - AI Slop Cleanup
-
-Senior maintainer performing periodic repo hygiene. Mission: remove AI-generated slop while preserving behavior and minimizing diffs.
-
-## Constraints (Priority Order)
-
-When constraints conflict, follow this priority:
-
-1. **Preserve behavior and public APIs** (highest priority)
-2. **Minimal diffs** - do not reformat unrelated code
-3. **Prefer deletion over invention**
-4. **No new dependencies or abstractions**
-5. **Respect repo conventions** (check CLAUDE.md/AGENTS.md)
-
-## Arguments
-
-Parse from $ARGUMENTS or use defaults:
-
-- **Mode**: `report` (default) or `apply`
-- **Scope**: `all` (default), `diff`, or path
-- **Thoroughness**: `quick`, `normal` (default), or `deep`
-
-## Execution
-
-### Phase 1: Spawn Deslop 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: Handle Mode
-
-#### Report Mode (Default)
-
-Present findings as markdown table:
-
-```markdown
-## Slop Hotspots
-
-| Priority | File | Issue | Certainty | Fix |
-|----------|------|-------|-----------|-----|
-| 1 | src/api.js:42 | console.log | HIGH | auto |
-| 2 | src/auth.js:15 | empty catch | HIGH | auto |
-| 3 | lib/utils.js:88 | excessive comments | MEDIUM | review |
-
-## Summary
-
-- **HIGH certainty**: N (auto-fixable)
-- **MEDIUM certainty**: N (review required)
-- **LOW certainty**: N (flagged only)
-
-## Do Next
-
-- [ ] Run `/deslop apply` to auto-fix HIGH certainty items
-- [ ] Review MEDIUM certainty items manually
-```
-
-#### Apply Mode
-
-If fixes array is non-empty, spawn simple-fixer:
-
-*(JavaScript reference - not executable in OpenCode)*
-
-Present results:
-
-```markdown
-## Applied Fixes
-
-| File | Line | Fix |
-|------|------|-----|
-| src/api.js | 42 | remove-line (console.log) |
-| src/auth.js | 15 | add-comment (empty catch) |
-
-**Total**: N fixes applied
-
-## Remaining (manual review needed)
-
-| File | Line | Issue | Certainty |
-|------|------|-------|-----------|
-| lib/utils.js | 88 | excessive comments | MEDIUM |
-```
-
-## Verification Strategy
-
-After fixes are applied, run project's test command:
-
-```bash
-npm test
-# or pytest, cargo test, go test ./...
-```
-
-On failure: `git restore .` and report which change failed.
-
-## Ignore Zones
-
-Skip these paths (handled by detection script):
-- Build artifacts: `dist/`, `build/`, `target/`, `out/`, `.next/`
-- Vendored: `vendor/`, `node_modules/`, `**/*.min.*`
-- Generated: `**/*.gen.*`, lockfiles
-
-## Error Handling
-
-- Git not available: Exit with "Git required for rollback safety"
-- Invalid scope path: Exit with "Path not found: <path>"
-- Verification fails: Rollback with `git restore .`, report failure
-
-## Additional Resources
-
-### Reference Files
-
-For detailed pattern documentation, consult:
-- **`references/slop-categories.md`** - All pattern categories, severity levels, certainty thresholds, auto-fix strategies
-
-### Scripts
-
-- **`scripts/detect.js`** - Detection pipeline CLI (run with `--help` for options)

package/adapters/opencode/commands/drift-detect.md

@@ -1,172 +0,0 @@
----
-description: Deep repository analysis to realign project plans with actual code reality
-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`
-
-
-# /drift-detect - Reality Check Scanner
-
-Perform deep repository analysis to identify drift between documented plans and actual implementation.
-
-## Architecture
-
-```
-scan.md → collectors.js (pure JS) → plan-synthesizer (Opus) → report
-          ├─ scanGitHubState()      (single call with full context)
-          ├─ analyzeDocumentation()
-          └─ scanCodebase()
-```
-
-Data collection is pure JavaScript (no LLM). Only semantic analysis uses Opus.
-
-## Arguments
-
-Parse from $ARGUMENTS:
-- `--sources`: Comma-separated list of sources to scan (default: github,docs,code)
-- `--depth`: Scan depth - quick or thorough (default: thorough)
-- `--output`: Output mode - file, display, or both (default: both)
-- `--file`: Output file path (default: drift-detect-report.md)
-
-Example: `/drift-detect --sources github,docs --depth quick --output file`
-
-## Phase 1: Parse Arguments and Collect Data
-
-*(JavaScript reference - not executable in OpenCode)*
-
-## Phase 2: Semantic Analysis (Single Opus Call)
-
-Send all collected data to plan-synthesizer for deep semantic analysis:
-
-*(JavaScript reference - not executable in OpenCode)*'}json
-${JSON.stringify(collectedData.github, null, 2)}
-${'```'}
-
-### Documentation Analysis
-${'```'}json
-${JSON.stringify(collectedData.docs, null, 2)}
-${'```'}
-
-### Codebase Analysis
-${'```'}json
-${JSON.stringify(collectedData.code, null, 2)}
-${'```'}
-
-## Your Task
-
-Be BRUTALLY SPECIFIC. The user wants concrete, actionable insights - not generic observations.
-
-### 1. Issue-by-Issue Verification
-
-For EACH open issue, determine:
-- Is this already implemented? → "Close issue #X - implemented in src/auth/login.js"
-- Is this stale/irrelevant? → "Close issue #X - no longer applicable after Y refactor"
-- Is this blocked? → "Issue #X blocked by: missing Z dependency"
-
-### 2. Phase/Checkbox Validation
-
-For EACH phase or checkbox marked "complete" in docs:
-- Verify against actual code: Does the feature exist?
-- Check for missing pieces: "Phase 'Authentication' marked complete but MISSING:
-  - Password reset functionality (no code in auth/)
-  - Session timeout handling (not implemented)
-  - Tests for login flow (0 test files)"
-
-### 3. Release Readiness Assessment
-
-If there are milestones or planned releases, assess:
-- "Your plan to release tomorrow is UNREALISTIC because:
-  - 3 critical tests missing for payment module
-  - No QA coverage on authentication flows
-  - Issue #45 (security) still open
-  - Phase B only 40% complete despite being marked done"
-
-### 4. Specific Recommendations
-
-Output SPECIFIC actions, not generic advice:
-- "Close issues: #12, #34, #56 (already implemented)"
-- "Reopen: Phase C (missing: X, Y, Z)"
-- "Block release until: tests added for auth/, issue #78 fixed"
-- "Update PLAN.md: Phase B is NOT complete - missing items listed above"
-
-## Output Format
-
-```markdown
-# Reality Check Report
-
-## Executive Summary
-[2-3 sentences: Overall project health and biggest concerns]
-
-## Issues to Close (Already Done)
-- #XX: [title] - Implemented in [file/location]
-- #YY: [title] - No longer relevant because [reason]
-
-## Phases Marked Complete But NOT Actually Done
-### [Phase Name]
-**Status in docs**: Complete [OK]
-**Actual status**: INCOMPLETE
-**Missing**:
-- [ ] [Specific missing item 1]
-- [ ] [Specific missing item 2]
-
-## Release Blockers
-If you're planning to ship soon, these MUST be addressed:
-1. [Specific blocker with file/issue reference]
-2. [Specific blocker with file/issue reference]
-
-## Issues That Need Attention
-- #XX: [why it's stale/blocked/misprioritized]
-
-## Quick Wins
-Things you can do right now:
-1. Close issue #XX (already done)
-2. Update Phase Y status (not complete)
-3. Add test for [specific untested code]
-```
-`;
-
-Invoke `@plan-synthesizer` agent
-```
-
-## Phase 3: Output Report
-
-After the synthesizer completes, the report is available. Handle output per settings:
-
-```javascript
-// The synthesizer outputs the report directly
-// Handle file writing if requested
-
-if (options.output === 'file' || options.output === 'both') {
-  console.log(`\n---\nReport saved to: ${options.file}`);
-}
-
-console.log(`
-## Reality Check Complete
-
-Use the findings above to realign your project with reality.
-Run \`/drift-detect --depth quick\` for faster subsequent scans.
-`);
-```
-
-## Quick Reference
-
-| Flag | Values | Default | Description |
-|------|--------|---------|-------------|
-| --sources | github,docs,code | all three | Which sources to scan |
-| --depth | quick, thorough | thorough | How deep to analyze |
-| --output | file, display, both | both | Where to output results |
-| --file | path | drift-detect-report.md | Output file path |
-
-## Success Criteria
-
-- Data collected via pure JavaScript (no LLM overhead)
-- Single Opus call for semantic analysis with full context
-- Drift and gaps clearly identified with examples
-- Prioritized reconstruction plan produced
-- Report output per user settings
-
-Begin scan now.

package/adapters/opencode/commands/enhance.md

@@ -1,182 +0,0 @@
----
-description: Analyze plugins, agents, prompts, docs, hooks, and skills for best-practice gaps
-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`
-
-
-# /enhance - Master Enhancement Orchestrator
-
-Run all enhancement analyzers in parallel and generate a unified report.
-
-## Overview
-
-The master `/enhance` command orchestrates 7 specialized enhancers:
-- **plugin** - Plugin structures, MCP tools, security patterns
-- **agent** - Agent prompts, frontmatter, tool restrictions
-- **claudemd** - CLAUDE.md/AGENTS.md project memory files
-- **docs** - Documentation structure and RAG optimization
-- **prompt** - General prompt quality and clarity
-- **hooks** - Hook definitions and frontmatter quality
-- **skills** - SKILL.md structure and trigger clarity
-
-## Arguments
-
-Parse from $ARGUMENTS:
-- **target-path**: Directory or file to analyze (default: current directory)
-- **--apply**: Apply auto-fixes for HIGH certainty issues after report
-- **--focus=TYPE**: Run only specified enhancer(s): plugin, agent, claudemd/claude-memory, docs, prompt, hooks, skills
-- **--verbose**: Include LOW certainty issues in report
-- **--show-suppressed**: Show what's being filtered by auto-learned suppressions
-- **--no-learn**: Disable auto-learning for this run (analyze but don't save)
-- **--reset-learned**: Clear all auto-learned suppressions for this project
-- **--export-learned**: Export learned suppressions as JSON for team sharing
-
-## Workflow
-
-1. **Discovery** - Detect what content types exist in target path
-2. **Load Suppressions** - Load auto-learned and manual suppressions for project
-3. **Launch** - Start all relevant enhancers in parallel via Task()
-4. **Aggregate** - Collect and deduplicate findings from all enhancers
-5. **Report** - Generate unified report from aggregated findings
-6. **Auto-Learn** - Detect false positives and save for future runs (unless --no-learn)
-7. **Fix** - Apply auto-fixes if --apply flag is present
-
-## Implementation
-
-Execute the `enhance-orchestrator` skill directly. The skill workflow:
-
-1. Parse arguments from $ARGUMENTS
-2. Run discovery to find content types
-3. Spawn enhancer agents in parallel via Task() for each content type
-4. Aggregate results from all enhancers
-5. Generate unified report
-
-See `skills/enhance-orchestrator/SKILL.md` for detailed implementation.
-
-## Output Format
-
-```markdown
-# Enhancement Analysis Report
-
-**Target**: {targetPath}
-**Date**: {timestamp}
-**Enhancers Run**: plugin, agent, docs
-
-## Executive Summary
-
-| Enhancer | HIGH | MEDIUM | LOW | Auto-Fixable |
-|----------|------|--------|-----|--------------|
-| plugin | 2 | 3 | 1 | 1 |
-| agent | 1 | 2 | 0 | 1 |
-| docs | 0 | 4 | 2 | 0 |
-| **Total** | **3** | **9** | **3** | **2** |
-
-## HIGH Certainty Issues (3)
-
-[Grouped by enhancer, sorted by file]
-
-## MEDIUM Certainty Issues (9)
-
-[...]
-
-## Auto-Fix Summary
-
-2 issues can be automatically fixed with `--apply` flag.
-```
-
-## Example Usage
-
-```bash
-# Full analysis of current directory
-/enhance
-
-# Focus on specific enhancer type
-/enhance --focus=agent
-
-# Apply auto-fixes for HIGH certainty issues
-/enhance --apply
-
-# Analyze specific path with verbose output
-/enhance plugins/next-task --verbose
-
-# Combined flags
-/enhance --focus=plugin --apply --verbose
-
-# Auto-Learning Suppression System
-# See what's being filtered by auto-learned suppressions
-/enhance --show-suppressed
-
-# Run without auto-learning (analyze only, don't save new suppressions)
-/enhance --no-learn
-
-# Reset all learned suppressions for this project
-/enhance --reset-learned
-
-# Export learned suppressions for team sharing
-/enhance --export-learned > suppressions-export.json
-```
-
-## Success Criteria
-
-- All relevant enhancers run in parallel
-- Findings deduplicated and sorted by certainty
-- Clear executive summary with counts
-- Auto-fixable issues highlighted
-- Fixes applied only with explicit --apply flag
-- Auto-learning detects false positives with 90%+ confidence
-- Learned suppressions stored in cross-platform location (${STATE_DIR}/enhance/suppressions.json)
-- Zero token waste on previously suppressed findings
-
----
-
-# /plugin
-
-Spawns `plugin-enhancer` agent which invokes `enhance-plugins` skill.
-See skill for patterns, detection logic, and auto-fix implementations.
-
----
-
-# /agent
-
-Spawns `agent-enhancer` agent which invokes `enhance-agent-prompts` skill.
-See skill for patterns, detection logic, and auto-fix implementations.
-
----
-
-# /docs
-
-Spawns `docs-enhancer` agent which invokes `enhance-docs` skill.
-See skill for patterns, detection logic, and auto-fix implementations.
-
----
-
-# /claudemd
-
-Spawns `claudemd-enhancer` agent which invokes `enhance-claude-memory` skill.
-See skill for patterns, detection logic, and auto-fix implementations.
-
----
-
-# /prompt
-
-Spawns `prompt-enhancer` agent which invokes `enhance-prompts` skill.
-See skill for patterns, detection logic, and auto-fix implementations.
-
----
-
-# /hooks
-
-Spawns `hooks-enhancer` agent which invokes `enhance-hooks` skill.
-See skill for patterns, detection logic, and auto-fix implementations.
-
----
-
-# /skills
-
-Spawns `skills-enhancer` agent which invokes `enhance-skills` skill.
-See skill for patterns, detection logic, and auto-fix implementations.