pi-cicd 1.0.10 → 1.0.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -2
  2. package/skills/intelligent-deploy/SKILL.md +0 -144
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-cicd",
3
- "version": "1.0.10",
3
+ "version": "1.0.11",
4
4
  "description": "Extension for Pi coding agent",
5
5
  "type": "module",
6
6
  "main": "./index.ts",
@@ -16,7 +16,6 @@
16
16
  "*.ts",
17
17
  "*.mjs",
18
18
  "src/**/*.ts",
19
- "skills/**/*",
20
19
  "README.md",
21
20
  "docs/",
22
21
  "CHANGELOG.md",
package/skills/intelligent-deploy/SKILL.md DELETED
@@ -1,144 +0,0 @@
1
- ---
2
- name: intelligent-deploy
3
- description: CI/CD pipeline monitoring, canary deployment management, and landing queue orchestration
4
- triggers:
5
- - deploy
6
- - canary
7
- - rollout
8
- - landing queue
9
- - production
10
- - CI status
11
- - pipeline
12
- - release
13
- - build
14
- requirements:
15
- tools: [bash]
16
- context: [CI configuration, deployment scripts]
17
- ---
18
-
19
- # Intelligent Deploy Skill
20
-
21
- ## Objective
22
- Monitor CI/CD pipelines, manage canary deployments, and track landing queues for safe production releases.
23
-
24
- ## Tools Available
25
- - `/ci` command - Show CI status and run information
26
- - `bash` - For running CI scripts and deployment commands
27
-
28
- ## When to Use
29
- - When deploying to production
30
- - When monitoring CI/CD pipelines
31
- - When managing canary releases
32
- - When tracking landing queues
33
- - When investigating build failures
34
- - When checking deployment status
35
-
36
- ## CI Status Command
37
-
38
- ### Usage
39
- ```
40
- /ci [run-id]
41
- ```
42
-
43
- Shows:
44
- - Current/last CI run status
45
- - Exit codes
46
- - Duration
47
- - Events
48
-
49
- ### Exit Codes
50
- | Code | Meaning |
51
- |------|---------|
52
- | 0 | Success |
53
- | 1 | General failure |
54
- | 2 | Misuse/Invalid input |
55
- | 3 | Configuration error |
56
- | 124 | Timeout |
57
- | 137 | SIGKILL (OOM) |
58
-
59
- ## Deployment Strategies
60
-
61
- ### Canary Deployment
62
- 1. Deploy to small percentage
63
- 2. Monitor metrics
64
- 3. Gradually increase
65
- 4. Full rollout or rollback
66
-
67
- ### Landing Queue
68
- - Queue changes for controlled rollout
69
- - Automatic promotion
70
- - Manual gates for risky changes
71
-
72
- ## Pipeline Monitoring
73
-
74
- ### Status Check
75
- ```
76
- /ci
77
- ```
78
-
79
- Returns:
80
- - Run ID
81
- - Start time
82
- - Events (pass/fail)
83
- - Exit code
84
- - Duration
85
-
86
- ### Historical Analysis
87
- Track patterns in:
88
- - Build times
89
- - Failure rates
90
- - Flaky tests
91
-
92
- ## Examples
93
-
94
- ### Check CI Status
95
- ```
96
- User: What's the CI status?
97
- Agent:
98
- /ci
99
- ```
100
-
101
- ### Check Specific Run
102
- ```
103
- Agent:
104
- /ci run-123
105
- ```
106
-
107
- ### Analyze Failure
108
- ```
109
- User: Why did the build fail?
110
- Agent:
111
- /ci
112
- # Analyze events and exit code
113
- ```
114
-
115
- ### Run Deployment
116
- ```bash
117
- # Deploy with canary
118
- ./scripts/deploy.sh --strategy=canary --initial=5%
119
-
120
- # Check deployment status
121
- /ci
122
- ```
123
-
124
- ## Configuration
125
-
126
- ### Pipeline Config
127
- ```yaml
128
- ci:
129
- timeout: 300
130
- retry: 2
131
- parallel: true
132
-
133
- deploy:
134
- strategy: canary
135
- canary:
136
- initial: 5%
137
- increment: 10%
138
- pause: 5m
139
- ```
140
-
141
- ## Integration
142
- - With pi-pipeline for verification gates
143
- - With pi-debug for error investigation
144
- - With pi-render for status display