pi-cicd 1.0.5 → 1.0.7

package/docs/stories/US-001-intelligent-deploy-tool.md

@@ -0,0 +1,27 @@
+# US-001: Intelligent Deploy Tool
+
+## User Story
+As an agent, I want to monitor CI/CD pipelines, manage canary deployments, and track landing queues so that I can safely deploy changes to production.
+
+## Status
+- [x] Implemented
+
+## Commands
+- `/ci` - CI status command
+
+## Features
+- CI run tracking
+- Canary deployment support
+- Landing queue management
+- Exit code resolution
+
+## Triggers
+- "deploy", "canary", "rollout", "landing queue", "production"
+
+## Acceptance Criteria
+- [x] CI status command shows run information
+- [x] Exit codes are properly resolved
+- [x] Can track deployment progress
+
+## Notes
+See `skills/intelligent-deploy/SKILL.md` for detailed usage.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-cicd",
-  "version": "1.0.5",
+  "version": "1.0.7",
   "description": "Extension for Pi coding agent",
   "type": "module",
   "main": "./index.ts",

package/skills/intelligent-deploy/SKILL.md

@@ -1,229 +1,144 @@
 ---
 name: intelligent-deploy
-description: Canary deployment with monitoring and landing queue management
+description: CI/CD pipeline monitoring, canary deployment management, and landing queue orchestration
 triggers:
   - deploy
   - canary
   - rollout
   - landing queue
   - production
+  - CI status
+  - pipeline
+  - release
+  - build
 requirements:
   tools: [bash]
-  context: [deployment target]
+  context: [CI configuration, deployment scripts]
 ---
 
 # Intelligent Deploy Skill
 
 ## Objective
-Execute safe deployments with canary monitoring, automatic rollback, and landing queue management.
+Monitor CI/CD pipelines, manage canary deployments, and track landing queues for safe production releases.
 
-## When to Use
-- When user asks to "deploy" or "ship to production"
-- When running CI/CD pipelines
-- When managing multiple deployments
-- When requiring gradual rollouts with monitoring
-
-## Workflow
-
-### Step 1: Canary Deployment
-```typescript
-import { CanaryDeploy } from '../../src/deploy/canary-deploy';
-
-const canary = new CanaryDeploy({
-  initialPercentage: 10,
-  incrementPercentage: 10,
-  stepInterval: 60000, // 1 minute
-  totalDuration: 300000, // 5 minutes
-  metrics: {
-    successRate: { min: 95 },
-    latency: { max: 500 },
-    errorRate: { max: 5 },
-  },
-});
-
-const result = await canary.deploy({
-  name: 'production',
-  url: 'https://api.example.com',
-  healthy: true,
-});
-
-console.log(canary.formatReport(result));
-```
-
-### Step 2: Landing Queue
-```typescript
-import { LandingQueue } from '../../src/deploy/landing-queue';
+## Tools Available
+- `/ci` command - Show CI status and run information
+- `bash` - For running CI scripts and deployment commands
 
-const queue = new LandingQueue();
+## When to Use
+- When deploying to production
+- When monitoring CI/CD pipelines
+- When managing canary releases
+- When tracking landing queues
+- When investigating build failures
+- When checking deployment status
 
-// Add to queue
-queue.enqueue('v1.2.0', 'production', 'New feature release');
-queue.enqueue('v1.2.1', 'production', 'Bug fix');
+## CI Status Command
 
-// Process queue
-while (true) {
-  const next = await queue.startNext();
-  if (!next) break;
-  
-  // Deploy
-  const success = await deploy(next);
-  
-  // Mark complete
-  queue.complete(next.id, success);
-  
-  if (!success) break; // Stop on failure
-}
+### Usage
 ```
-
-### Step 3: Monitor and Rollback
-```typescript
-// Automatic rollback on issues
-if (result.rolledBack) {
-  console.log('Deployment rolled back due to issues');
-  await canary.rollback(target);
-}
+/ci [run-id]
 ```
 
-## Canary Configuration
+Shows:
+- Current/last CI run status
+- Exit codes
+- Duration
+- Events
 
-| Parameter | Default | Description |
-|-----------|---------|-------------|
-| initialPercentage | 10% | Starting traffic |
-| incrementPercentage | 10% | Traffic increase per step |
-| stepInterval | 1 min | Time between increments |
-| totalDuration | 5 min | Total deployment time |
+### Exit Codes
+| Code | Meaning |
+|------|---------|
+| 0 | Success |
+| 1 | General failure |
+| 2 | Misuse/Invalid input |
+| 3 | Configuration error |
+| 124 | Timeout |
+| 137 | SIGKILL (OOM) |
 
-### Metrics Thresholds
+## Deployment Strategies
 
-| Metric | Threshold | Action |
-|--------|-----------|--------|
-| Success Rate | > 95% | Continue |
-| Latency | < 500ms | Continue |
-| Error Rate | < 5% | Continue |
+### Canary Deployment
+1. Deploy to small percentage
+2. Monitor metrics
+3. Gradually increase
+4. Full rollout or rollback
 
-If metrics drop below thresholds:
-- Warning at threshold
-- Auto-rollback at critical level (90% success, 10% errors)
+### Landing Queue
+- Queue changes for controlled rollout
+- Automatic promotion
+- Manual gates for risky changes
 
-## Landing Queue Commands
+## Pipeline Monitoring
 
-### Enqueue Deployment
-```typescript
-queue.enqueue('v1.2.0', 'production', 'Feature release');
+### Status Check
 ```
-
-### Process Queue
-```typescript
-while (const next = queue.startNext()) {
-  await deploy(next);
-  queue.complete(next.id, success);
-}
+/ci
 ```
 
-### View Status
-```typescript
-console.log(queue.formatReport());
-```
+Returns:
+- Run ID
+- Start time
+- Events (pass/fail)
+- Exit code
+- Duration
+
+### Historical Analysis
+Track patterns in:
+- Build times
+- Failure rates
+- Flaky tests
 
 ## Examples
 
-### Deploy with Canary
+### Check CI Status
 ```
-User: Deploy v1.2.0 to production with canary
+User: What's the CI status?
 Agent:
-  const result = await canary.deploy({ name: 'production', url: '...', healthy: true });
-  if (result.success) {
-    console.log('Deployment successful!');
-  } else {
-    console.log('Rolled back - check issues');
-  }
+  /ci
 ```
 
-### Process Landing Queue
+### Check Specific Run
 ```
-User: Queue these deployments: v1.2.0, v1.2.1, v1.2.2
 Agent:
-  queue.enqueue('v1.2.0', 'production');
-  queue.enqueue('v1.2.1', 'production');
-  queue.enqueue('v1.2.2', 'staging');
-  
-  const result = await queue.processAll();
+  /ci run-123
 ```
 
-### View Queue Status
+### Analyze Failure
 ```
-User: Show me the current deployment queue
+User: Why did the build fail?
 Agent:
-  console.log(queue.formatReport());
-```
-
-## Output Format
-
-### Canary Report
-```markdown
-## Canary Deployment Report
-**Status:** ✅ SUCCESS
-**Final Traffic:** 100%
-**Rolled Back:** No
-
-### Metrics History
-| Time | Success | Latency | Error Rate |
-|------|---------|---------|------------|
-| 0min | 98.5% | 120ms | 1.2% |
-| 1min | 99.1% | 115ms | 0.8% |
-| 2min | 99.3% | 110ms | 0.5% |
+  /ci
+  # Analyze events and exit code
 ```
 
-### Landing Queue Report
-```markdown
-## Landing Queue Report
-**Total:** 5 | **Pending:** 2 | **Deploying:** 1 | **Deployed:** 2 | **Failed:** 0
+### Run Deployment
+```bash
+# Deploy with canary
+./scripts/deploy.sh --strategy=canary --initial=5%
 
-### Currently Deploying
-**v1.2.1** -> production
-Status: deploying
-
-### Queue
-| # | Version | Environment | Message |
-|---|--------|------------|---------|
-| 1 | v1.2.2 | production | Hotfix |
-| 2 | v1.2.3 | staging | New feature |
+# Check deployment status
+/ci
 ```
 
-## Integration
+## Configuration
 
-### With pi-pipeline
-```typescript
-// Run as part of ship workflow
-const gates = new QualityGates();
-const gatesResult = await gates.run('pre-push');
-
-if (gatesResult.passed) {
-  const result = await canary.deploy(target);
-  if (!result.success) {
-    throw new Error('Deployment failed');
-  }
-}
-```
-
-### With pi-audit
-```typescript
-// Security scan before deploy
-const shield = new AgentShield();
-const scan = shield.scan(deploymentCode);
-
-if (!scan.passed) {
-  console.log('Security issues must be fixed');
-  process.exit(1);
-}
+### Pipeline Config
+```yaml
+ci:
+  timeout: 300
+  retry: 2
+  parallel: true
+  
+deploy:
+  strategy: canary
+  canary:
+    initial: 5%
+    increment: 10%
+    pause: 5m
 ```
 
-### With pi-recollect
-```typescript
-// Remember deployment
-await memory.remember(
-  'deployment',
-  `Deployed ${version} to ${environment}`,
-  'observation'
-);
-```
+## Integration
+- With pi-pipeline for verification gates
+- With pi-debug for error investigation
+- With pi-render for status display