claude-autopm 2.8.1 → 2.8.3

package/packages/plugin-cloud/scripts/examples/azure-setup.sh

@@ -0,0 +1,33 @@
+#!/usr/bin/env bash
+# Azure environment setup example
+# Usage: ./azure-setup.sh
+
+set -euo pipefail
+
+echo "🔍 Setting up Azure environment..."
+
+# Check Azure CLI is installed
+if ! command -v az &> /dev/null; then
+    echo "❌ Azure CLI not found. Please install it first."
+    exit 1
+fi
+
+# Check login status
+echo "📋 Checking Azure login status..."
+az account show || {
+    echo "🔐 Not logged in. Starting login..."
+    az login
+}
+
+# List subscriptions
+echo "📋 Available subscriptions:"
+az account list --output table
+
+# Set default subscription (if needed)
+# az account set --subscription "Your-Subscription-Name"
+
+# Validate resource providers
+echo "🔍 Checking resource providers..."
+az provider list --query "[?registrationState=='Registered'].namespace" --output table
+
+echo "✅ Azure environment setup complete"

package/packages/plugin-cloud/scripts/examples/gcp-setup.sh

@@ -0,0 +1,39 @@
+#!/usr/bin/env bash
+# GCP environment setup example
+# Usage: ./gcp-setup.sh [project-id]
+
+set -euo pipefail
+
+PROJECT_ID="${1:-}"
+
+echo "🔍 Setting up GCP environment..."
+
+# Check gcloud CLI is installed
+if ! command -v gcloud &> /dev/null; then
+    echo "❌ gcloud CLI not found. Please install it first."
+    exit 1
+fi
+
+# Check login status
+echo "📋 Checking GCP login status..."
+gcloud auth list
+
+# Set project if provided
+if [ -n "$PROJECT_ID" ]; then
+    echo "🔧 Setting project to: $PROJECT_ID"
+    gcloud config set project "$PROJECT_ID"
+fi
+
+# List projects
+echo "📋 Available projects:"
+gcloud projects list
+
+# Show current configuration
+echo "⚙️  Current configuration:"
+gcloud config list
+
+# Enable required APIs (example)
+# gcloud services enable compute.googleapis.com
+# gcloud services enable container.googleapis.com
+
+echo "✅ GCP environment setup complete"

package/packages/plugin-cloud/scripts/examples/k8s-validate.sh

@@ -0,0 +1,40 @@
+#!/usr/bin/env bash
+# Kubernetes cluster validation example
+# Usage: ./k8s-validate.sh [context]
+
+set -euo pipefail
+
+CONTEXT="${1:-$(kubectl config current-context)}"
+
+echo "🔍 Validating Kubernetes cluster: ${CONTEXT}..."
+
+# Check kubectl is installed
+if ! command -v kubectl &> /dev/null; then
+    echo "❌ kubectl not found. Please install it first."
+    exit 1
+fi
+
+# Use specified context
+kubectl config use-context "$CONTEXT"
+
+# Check cluster info
+echo "📋 Cluster info:"
+kubectl cluster-info
+
+# Check nodes
+echo "🖥️  Cluster nodes:"
+kubectl get nodes
+
+# Check system pods
+echo "🐳 System pods:"
+kubectl get pods -n kube-system
+
+# Check namespaces
+echo "📁 Namespaces:"
+kubectl get namespaces
+
+# Validate RBAC (if you have permissions)
+echo "🔐 Checking RBAC..."
+kubectl auth can-i --list || echo "⚠️  RBAC check requires additional permissions"
+
+echo "✅ Kubernetes cluster validation complete for: ${CONTEXT}"

package/packages/plugin-cloud/scripts/examples/terraform-init.sh

@@ -0,0 +1,26 @@
+#!/usr/bin/env bash
+# Terraform initialization and validation example
+# Usage: ./terraform-init.sh [environment]
+
+set -euo pipefail
+
+ENVIRONMENT="${1:-staging}"
+
+echo "🚀 Initializing Terraform for ${ENVIRONMENT} environment..."
+
+# Initialize Terraform
+terraform init -backend-config="env/${ENVIRONMENT}/backend.tf"
+
+# Validate configuration
+terraform validate
+
+# Format check
+terraform fmt -check -recursive
+
+# Security scan (if tfsec is installed)
+if command -v tfsec &> /dev/null; then
+    echo "🔒 Running security scan..."
+    tfsec .
+fi
+
+echo "✅ Terraform initialization complete for ${ENVIRONMENT}"

package/packages/plugin-core/README.md

@@ -0,0 +1,274 @@
+# @claudeautopm/plugin-core
+
+> Core framework functionality for ClaudeAutoPM
+
+**Version:** 2.0.0
+**Category:** Core Framework
+**Size:** ~8 KB (gzipped)
+**Status:** ✅ Required (always installed)
+
+---
+
+## Overview
+
+This is the **core framework plugin** that provides essential functionality for ClaudeAutoPM. It includes universal agents, rules, hooks, and utilities that apply to ALL projects regardless of technology stack.
+
+**This plugin is REQUIRED** and is automatically installed with ClaudeAutoPM.
+
+---
+
+## What's Included
+
+### 🤖 Agents (4)
+
+Core agents for framework functionality:
+
+1. **agent-manager** - Create, analyze, and manage agents in the registry
+2. **code-analyzer** - Analyze code changes for bugs, trace logic flow, investigate issues
+3. **test-runner** - Run tests and provide comprehensive analysis of results
+4. **file-analyzer** - Analyze and summarize large files to reduce context usage
+
+### 📋 Commands (3)
+
+Framework utility commands:
+
+1. **code-rabbit** - Process CodeRabbit review comments with context-aware discretion
+2. **prompt** - Handle complex prompts with many @ references
+3. **re-init** - Reinitialize CLAUDE.md with framework rules
+
+### 📜 Rules (23)
+
+Universal rules that apply to all projects:
+
+**Critical Priority:**
+- `tdd.enforcement` - Enforce Test-Driven Development (Red-Green-Refactor)
+- `context7-enforcement` - Enforce Context7 documentation queries
+- `framework-path-rules` - Path convention enforcement
+- `golden-rules` - Core framework principles
+- `security-checklist` - Universal security standards
+
+**High Priority:**
+- `agent-coordination` - Agent orchestration patterns
+- `agent-mandatory` - Agent usage requirements
+- `command-pipelines` - Command orchestration
+- `development-workflow` - Universal development workflow
+- `git-strategy` - Git workflow and branching
+- `definition-of-done` - Quality standards
+- `pipeline-mandatory` - Pipeline enforcement
+
+**Medium Priority:**
+- `ai-integration-patterns` - AI integration best practices
+- `context-optimization` - Context management strategies
+- `development-environments` - Environment setup
+- `naming-conventions` - Naming standards
+- `no-pr-workflow` - Alternative git workflow
+- `performance-guidelines` - Performance optimization
+- `standard-patterns` - Universal coding patterns
+
+**Low Priority:**
+- `datetime` - Date/time handling conventions
+- `frontmatter-operations` - Frontmatter parsing
+- `strip-frontmatter` - Frontmatter utilities
+- `use-ast-grep` - AST parsing utilities
+
+### 🪝 Hooks (7)
+
+Enforcement hooks for framework behavior:
+
+**Context7 Enforcement:**
+- `pre-command-context7.js` - Enforce Context7 queries before command execution (BLOCKING)
+- `pre-agent-context7.js` - Enforce Context7 queries before agent invocation (BLOCKING)
+- `unified-context7-enforcement.sh` - Unified Context7 wrapper
+- `context7-reminder.md` - Context7 reminder text
+
+**Agent Enforcement:**
+- `enforce-agents.js` + `.sh` - Enforce agent usage over direct tool calls (BLOCKING)
+- `strict-enforce-agents.sh` - Stricter agent enforcement (BLOCKING)
+
+**Testing:**
+- `test-hook.sh` - Hook testing utility
+
+### 📦 Scripts (10)
+
+Framework utilities and libraries:
+
+**lib/ - Shared Libraries (5 scripts):**
+- `datetime-utils.sh` - Date and time utilities
+- `frontmatter-utils.sh` - Markdown frontmatter parsing
+- `github-utils.sh` - GitHub API utilities
+- `logging-utils.sh` - Logging utilities
+- `validation-utils.sh` - Validation utilities
+
+**mcp/ - MCP Management (5 scripts):**
+- `add.sh` - Add MCP server
+- `enable.sh` - Enable MCP server
+- `disable.sh` - Disable MCP server
+- `list.sh` - List MCP servers
+- `sync.sh` - Sync MCP configuration
+
+---
+
+## Installation
+
+This plugin is **automatically installed** with ClaudeAutoPM. No manual installation needed.
+
+```bash
+# When you install ClaudeAutoPM:
+npm install -g claudeautopm
+autopm init
+
+# plugin-core is automatically included
+```
+
+---
+
+## Features
+
+### TDD Enforcement ✅
+
+**Always enabled** - Enforces Test-Driven Development:
+- Red-Green-Refactor cycle mandatory
+- Tests MUST be written before implementation
+- 100% test coverage for new code
+- Zero tolerance policy
+
+```bash
+# Enforced by: rules/tdd.enforcement.md
+```
+
+### Context7 Enforcement ✅
+
+**Always enabled** - Enforces Context7 documentation queries:
+- MUST query Context7 before ALL command/agent execution
+- Live documentation verification
+- API signature validation
+- Zero tolerance policy
+
+```bash
+# Enforced by:
+# - rules/context7-enforcement.md
+# - hooks/pre-command-context7.js
+# - hooks/pre-agent-context7.js
+```
+
+### Agent Coordination ✅
+
+**Always enabled** - Agent orchestration and coordination:
+- Agent selection patterns
+- Parallel vs sequential execution
+- Error handling in agent workflows
+- Context management between agents
+
+```bash
+# Enforced by: rules/agent-coordination.md
+```
+
+### MCP Management ✅
+
+**Always enabled** - MCP server management utilities:
+- Add/enable/disable MCP servers
+- List configured servers
+- Sync MCP configuration
+
+```bash
+# Provided by: scripts/mcp/*.sh
+```
+
+---
+
+## Usage
+
+### Using Core Agents
+
+```bash
+# Invoke agents directly
+@agent-manager create a new specialized agent for GraphQL
+@code-analyzer review recent changes for bugs
+@test-runner execute full test suite with analysis
+@file-analyzer summarize large-log-file.log
+```
+
+### Using Core Commands
+
+```bash
+# Process CodeRabbit reviews
+/code-rabbit
+
+# Handle complex prompts
+/prompt
+
+# Reinitialize framework
+/re-init
+```
+
+### Using Scripts
+
+```bash
+# Use utility libraries (sourced by other scripts)
+source .claude/scripts/lib/github-utils.sh
+source .claude/scripts/lib/logging-utils.sh
+
+# MCP management
+bash .claude/scripts/mcp/add.sh context7
+bash .claude/scripts/mcp/list.sh
+bash .claude/scripts/mcp/sync.sh
+```
+
+---
+
+## Dependencies
+
+### Peer Dependencies
+
+None - this is the base plugin.
+
+### Required By
+
+All other plugins depend on `plugin-core`:
+- `@claudeautopm/plugin-pm` - PM workflows
+- `@claudeautopm/plugin-devops` - DevOps automation
+- `@claudeautopm/plugin-cloud` - Cloud infrastructure
+- `@claudeautopm/plugin-frameworks` - Frontend frameworks
+- `@claudeautopm/plugin-databases` - Databases
+- `@claudeautopm/plugin-languages` - Programming languages
+- `@claudeautopm/plugin-data` - Data engineering
+
+---
+
+## Configuration
+
+No configuration needed - all core features are always enabled.
+
+---
+
+## Size and Performance
+
+- **Package size:** ~8 KB (gzipped) / ~80 KB (uncompressed)
+- **Installation time:** < 1 second
+- **Memory footprint:** Minimal (utilities loaded on-demand)
+
+---
+
+## Compatibility
+
+- **Minimum ClaudeAutoPM version:** 3.0.0
+- **Node.js:** >= 18.0.0
+- **Platform:** Cross-platform (macOS, Linux, Windows)
+
+---
+
+## License
+
+MIT
+
+---
+
+## Support
+
+- **Issues:** https://github.com/rafeekpro/ClaudeAutoPM/issues
+- **Documentation:** https://github.com/rafeekpro/ClaudeAutoPM#readme
+- **Changelog:** See [CHANGELOG.md](../../CHANGELOG.md)
+
+---
+
+**Part of ClaudeAutoPM v3.0.0 Plugin Architecture**

package/packages/plugin-core/commands/code-rabbit.md

@@ -0,0 +1,128 @@
+---
+allowed-tools: Task, Read, Edit, MultiEdit, Write, LS, Grep
+---
+
+# CodeRabbit Review Handler
+
+Process CodeRabbit review comments with context-aware discretion.
+
+## Usage
+
+```
+/code-rabbit
+```
+
+Then paste one or more CodeRabbit comments.
+
+## Instructions
+
+### 1. Initial Context
+
+Inform the user:
+
+```
+I'll review the CodeRabbit comments with discretion, as CodeRabbit doesn't have access to the entire codebase and may not understand the full context.
+
+For each comment, I'll:
+- Evaluate if it's valid given our codebase context
+- Accept suggestions that improve code quality
+- Ignore suggestions that don't apply to our architecture
+- Explain my reasoning for accept/ignore decisions
+```
+
+### 2. Process Comments
+
+#### Single File Comments
+
+If all comments relate to one file:
+
+- Read the file for context
+- Evaluate each suggestion
+- Apply accepted changes in batch using MultiEdit
+- Report which suggestions were accepted/ignored and why
+
+#### Multiple File Comments
+
+If comments span multiple files:
+
+Launch parallel sub-agents using Task tool:
+
+```yaml
+Task:
+  description: "CodeRabbit fixes for {filename}"
+  subagent_type: "general-purpose"
+  prompt: |
+    Review and apply CodeRabbit suggestions for {filename}.
+    
+    Comments to evaluate:
+    {relevant_comments_for_this_file}
+    
+    Instructions:
+    1. Read the file to understand context
+    2. For each suggestion:
+       - Evaluate validity given codebase patterns
+       - Accept if it improves quality/correctness
+       - Ignore if not applicable
+    3. Apply accepted changes using Edit/MultiEdit
+    4. Return summary:
+       - Accepted: {list with reasons}
+       - Ignored: {list with reasons}
+       - Changes made: {brief description}
+    
+    Use discretion - CodeRabbit lacks full context.
+```
+
+### 3. Consolidate Results
+
+After all sub-agents complete:
+
+```
+📋 CodeRabbit Review Summary
+
+Files Processed: {count}
+
+Accepted Suggestions:
+  {file}: {changes_made}
+  
+Ignored Suggestions:
+  {file}: {reason_ignored}
+
+Overall: {X}/{Y} suggestions applied
+```
+
+### 4. Common Patterns to Ignore
+
+- **Style preferences** that conflict with project conventions
+- **Generic best practices** that don't apply to our specific use case
+- **Performance optimizations** for code that isn't performance-critical
+- **Accessibility suggestions** for internal tools
+- **Security warnings** for already-validated patterns
+- **Import reorganization** that would break our structure
+
+### 5. Common Patterns to Accept
+
+- **Actual bugs** (null checks, error handling)
+- **Security vulnerabilities** (unless false positive)
+- **Resource leaks** (unclosed connections, memory leaks)
+- **Type safety issues** (TypeScript/type hints)
+- **Logic errors** (off-by-one, incorrect conditions)
+- **Missing error handling**
+
+## Decision Framework
+
+For each suggestion, consider:
+
+1. **Is it correct?** - Does the issue actually exist?
+2. **Is it relevant?** - Does it apply to our use case?
+3. **Is it beneficial?** - Will fixing it improve the code?
+4. **Is it safe?** - Could the change introduce problems?
+
+Only apply if all answers are "yes" or the benefit clearly outweighs risks.
+
+## Important Notes
+
+- CodeRabbit is helpful but lacks context
+- Trust your understanding of the codebase over generic suggestions
+- Explain decisions briefly to maintain audit trail
+- Batch related changes for efficiency
+- Use parallel agents for multi-file reviews to save time

package/packages/plugin-core/commands/prompt.md

@@ -0,0 +1,9 @@
+---
+allowed-tools: Bash, Read, Write, LS
+---
+
+# This is an ephemeral command
+
+Some complex prompts (with numerous @ references) may fail if entered directly into the prompt input.
+
+If that happens, write your prompt here and type in `/prompt` in the prompt command.

package/packages/plugin-core/commands/re-init.md

@@ -0,0 +1,9 @@
+---
+allowed-tools: Bash, Read, Write, LS
+---
+
+# Enhance CLAUDE.md file
+
+Please update CLAUDE.md with the rules from .claude/CLAUDE.md.
+
+If CLAUDE.md does not exist, create it using the /init and include rules from .claude/CLAUDE.md.

package/packages/plugin-core/hooks/context7-reminder.md

@@ -0,0 +1,29 @@
+# 🔴 MANDATORY: Context7 Query Required
+
+**BEFORE proceeding with this command/agent, you MUST:**
+
+1. **Read** the command/agent file to find `**Documentation Queries:**` section
+2. **Query Context7 MCP** for EACH listed topic
+3. **Verify** patterns against live documentation
+4. **Apply** Context7 guidance in your implementation
+
+## Why This Matters
+
+- **Training data is STALE** - APIs change, best practices evolve
+- **Context7 is CURRENT** - Live documentation, latest versions
+- **Hallucinations PREVENTED** - Real examples, verified patterns
+- **Quality GUARANTEED** - Industry-standard approaches
+
+## Zero Tolerance Policy
+
+❌ **NO** implementation without Context7 verification
+❌ **NO** "I remember how this works"
+❌ **NO** assumptions about API signatures
+✅ **ALWAYS** query Context7 first
+✅ **ALWAYS** verify against live docs
+✅ **ALWAYS** apply documented patterns
+
+---
+
+*This reminder is shown by `.claude/hooks/` enforcement system*
+*Defined in: `.claude/rules/context7-enforcement.md`*