shipping-methodology

Name: shipping-methodology
Author: elb-pr

126stars7forks

How to install shipping-methodology?

elb-pr/claudikins-kernel/shipping-methodology

$npx -y skills add elb-pr/claudikins-kernel --skill shipping-methodology

Installs into the current project.

Summary

Use when running claudikins-kernel:ship, preparing PRs, writing changelogs, deciding merge strategy, or handling CI failures — enforces GRFP-style iterative approval, code integrity validation, and human-gated merges

Files · 1

View on GitHub

SKILL.md

1	# Shipping Methodology
2
3	## When to use this skill
4
5	Use this skill when you need to:
6
7	- Run the `claudikins-kernel:ship` command
8	- Prepare commit messages and PR descriptions
9	- Update changelogs and documentation
10	- Decide merge strategy (squash vs preserve)
11	- Handle CI failures or merge conflicts
12	- Validate code integrity before shipping
13
14	## Core Philosophy
15
16	> "Ship with confidence, not hope." - Shipping philosophy
17
18	Shipping is the final gate. Apply GRFP-style iterative workflow to every stage.
19
20	### The Five Principles
21
22	1. Gate check first - claudikins-kernel:verify must have passed. No exceptions.
23	2. Code integrity - Ship exactly what was verified. No sneaky changes.
24	3. GRFP everywhere - Section-by-section approval at every stage.
25	4. Human decides - No auto-merging. Human approves final merge.
26	5. Clean up after - Delete branches, update docs, celebrate.
27
28	## The Five Stages
29
30	### Stage 1: Pre-Ship Review
31
32	Show what's being shipped. Human confirms ready.
33
34	\| Check \| What to Show \|
35	\| ------------------- \| ----------------------------------------------- \|
36	\| Verification status \| All phases PASS from claudikins-kernel:verify \|
37	\| Branches to merge \| List all execute/task-\* branches \|
38	\| Evidence summary \| Screenshots, curl responses from catastrophiser \|
39	\| Code delta \| Lines added/removed, files changed \|
40
41	Checkpoint:
42
43	```
44	Ready to ship?
45
46	Verified: ✓ All checks passed
47	Branches: 3 branches to merge
48	Changes: +450 / -120 lines
49
50	[Continue] [Back to Verify] [Abort]
51	```
52
53	### Stage 2: Commit Strategy
54
55	Draft commit message(s). Human approves.
56
57	Decision:
58
59	```
60	How should we commit?
61
62	[Squash into single commit] [Preserve commit history]
63	```
64
65	Squash (recommended for features):
66
67	- Single clean commit on main
68	- Clear feature boundary
69	- Easier to revert if needed
70
71	Preserve (for large multi-part work):
72
73	- Keeps granular history
74	- Better for debugging
75	- Use for multi-feature batches
76
77	Checkpoint:
78
79	```
80	Commit message:
81
82	feat(auth): Add authentication middleware
83
84	- JWT token validation
85	- Role-based access control
86	- Session management
87
88	Closes #42
89
90	[Accept] [Revise] [Back]
91	```
92
93	### Stage 3: Documentation (git-perfectionist)
94
95	Update README, CHANGELOG, version. GRFP-style.
96
97	git-perfectionist uses github-readme plugin:
98
99	1. Deep-dive on current docs
100	2. Identify gaps from changes
101	3. Pen-wielding for updates
102	4. Section-by-section approval
103
104	Files to update:
105
106	\| File \| What to Update \|
107	\| ------------------------------------------ \| ---------------------------------------- \|
108	\| README.md \| Features, usage, installation if changed \|
109	\| CHANGELOG.md \| Add entry in Keep a Changelog format \|
110	\| package.json / Cargo.toml / pyproject.toml \| Version bump if needed \|
111
112	Checkpoint:
113
114	```
115	Documentation updates:
116
117	README.md:
118	- Added: Authentication section
119	- Updated: Installation (new deps)
120
121	CHANGELOG.md:
122	- Added: v1.2.0 entry
123
124	Version: 1.1.0 → 1.2.0 (minor)
125
126	[Accept] [Revise] [Skip]
127	```
128
129	### Stage 4: PR Creation
130
131	Draft PR title and body. Section-by-section approval.
132
133	PR Title Pattern:
134
135	```
136	feat(scope): Short description
137	```
138
139	PR Body Structure:
140
141	```markdown
142	## Summary
143
144	[2-3 bullet points of what changed]
145
146	## Changes
147
148	[Detailed breakdown]
149
150	## Testing
151
152	[How it was verified]
153
154	## Screenshots
155
156	[If applicable]
157	```
158
159	Checkpoint:
160
161	```
162	PR ready to create:
163
164	Title: feat(auth): Add authentication middleware
165
166	Body:
167	## Summary
168	- Added JWT token validation
169	- Implemented role-based access control
170	...
171
172	[Create PR] [Revise] [Back]
173	```
174
175	### Stage 5: Final Merge
176
177	CI passes. Human approves. Merge and cleanup.
178
179	CI Status Check:
180
181	```
182	CI Status: ⏳ Running...
183
184	[Wait for CI] [View logs] [Merge anyway]
185	```
186
187	On CI pass:
188
189	```
190	CI Status: ✓ All checks passed
191
192	Ready to merge PR #42 to main?
193
194	[Merge] [Request review first] [Cancel]
195	```
196
197	After merge:
198
199	- Delete feature branches (unless --no-delete-branch)
200	- Update ship-state.json
201	- Celebrate
202
203	Final output:
204
205	```
206	Done! Shipped to main.
207
208	PR #42 merged ✓
209	Branches cleaned up ✓
210	Version: 1.1.0 → 1.2.0
211
212	Nice work!
213	```
214
215	## Rationalizations to Resist
216
217	Agents under pressure find excuses. These are all violations:
218
219	\| Excuse \| Reality

People who liked this also viewed

6 picks

Type

shipping-methodology

126stars7forks

View on GitHub

How to install shipping-methodology?

elb-pr/claudikins-kernel/shipping-methodology

$npx -y skills add elb-pr/claudikins-kernel --skill shipping-methodology

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Shipping Methodology
2
3	## When to use this skill
4
5	Use this skill when you need to:
6
7	- Run the `claudikins-kernel:ship` command
8	- Prepare commit messages and PR descriptions
9	- Update changelogs and documentation
10	- Decide merge strategy (squash vs preserve)
11	- Handle CI failures or merge conflicts
12	- Validate code integrity before shipping
13
14	## Core Philosophy
15
16	> "Ship with confidence, not hope." - Shipping philosophy
17
18	Shipping is the final gate. Apply GRFP-style iterative workflow to every stage.
19
20	### The Five Principles
21
22	1. Gate check first - claudikins-kernel:verify must have passed. No exceptions.
23	2. Code integrity - Ship exactly what was verified. No sneaky changes.
24	3. GRFP everywhere - Section-by-section approval at every stage.
25	4. Human decides - No auto-merging. Human approves final merge.
26	5. Clean up after - Delete branches, update docs, celebrate.
27
28	## The Five Stages
29
30	### Stage 1: Pre-Ship Review
31
32	Show what's being shipped. Human confirms ready.
33
34	\| Check \| What to Show \|
35	\| ------------------- \| ----------------------------------------------- \|
36	\| Verification status \| All phases PASS from claudikins-kernel:verify \|
37	\| Branches to merge \| List all execute/task-\* branches \|
38	\| Evidence summary \| Screenshots, curl responses from catastrophiser \|
39	\| Code delta \| Lines added/removed, files changed \|
40
41	Checkpoint:
42
43	```
44	Ready to ship?
45
46	Verified: ✓ All checks passed
47	Branches: 3 branches to merge
48	Changes: +450 / -120 lines
49
50	[Continue] [Back to Verify] [Abort]
51	```
52
53	### Stage 2: Commit Strategy
54
55	Draft commit message(s). Human approves.
56
57	Decision:
58
59	```
60	How should we commit?
61
62	[Squash into single commit] [Preserve commit history]
63	```
64
65	Squash (recommended for features):
66
67	- Single clean commit on main
68	- Clear feature boundary
69	- Easier to revert if needed
70
71	Preserve (for large multi-part work):
72
73	- Keeps granular history
74	- Better for debugging
75	- Use for multi-feature batches
76
77	Checkpoint:
78
79	```
80	Commit message:
81
82	feat(auth): Add authentication middleware
83
84	- JWT token validation
85	- Role-based access control
86	- Session management
87
88	Closes #42
89
90	[Accept] [Revise] [Back]
91	```
92
93	### Stage 3: Documentation (git-perfectionist)
94
95	Update README, CHANGELOG, version. GRFP-style.
96
97	git-perfectionist uses github-readme plugin:
98
99	1. Deep-dive on current docs
100	2. Identify gaps from changes
101	3. Pen-wielding for updates
102	4. Section-by-section approval
103
104	Files to update:
105
106	\| File \| What to Update \|
107	\| ------------------------------------------ \| ---------------------------------------- \|
108	\| README.md \| Features, usage, installation if changed \|
109	\| CHANGELOG.md \| Add entry in Keep a Changelog format \|
110	\| package.json / Cargo.toml / pyproject.toml \| Version bump if needed \|
111
112	Checkpoint:
113
114	```
115	Documentation updates:
116
117	README.md:
118	- Added: Authentication section
119	- Updated: Installation (new deps)
120
121	CHANGELOG.md:
122	- Added: v1.2.0 entry
123
124	Version: 1.1.0 → 1.2.0 (minor)
125
126	[Accept] [Revise] [Skip]
127	```
128
129	### Stage 4: PR Creation
130
131	Draft PR title and body. Section-by-section approval.
132
133	PR Title Pattern:
134
135	```
136	feat(scope): Short description
137	```
138
139	PR Body Structure:
140
141	```markdown
142	## Summary
143
144	[2-3 bullet points of what changed]
145
146	## Changes
147
148	[Detailed breakdown]
149
150	## Testing
151
152	[How it was verified]
153
154	## Screenshots
155
156	[If applicable]
157	```
158
159	Checkpoint:
160
161	```
162	PR ready to create:
163
164	Title: feat(auth): Add authentication middleware
165
166	Body:
167	## Summary
168	- Added JWT token validation
169	- Implemented role-based access control
170	...
171
172	[Create PR] [Revise] [Back]
173	```
174
175	### Stage 5: Final Merge
176
177	CI passes. Human approves. Merge and cleanup.
178
179	CI Status Check:
180
181	```
182	CI Status: ⏳ Running...
183
184	[Wait for CI] [View logs] [Merge anyway]
185	```
186
187	On CI pass:
188
189	```
190	CI Status: ✓ All checks passed
191
192	Ready to merge PR #42 to main?
193
194	[Merge] [Request review first] [Cancel]
195	```
196
197	After merge:
198
199	- Delete feature branches (unless --no-delete-branch)
200	- Update ship-state.json
201	- Celebrate
202
203	Final output:
204
205	```
206	Done! Shipped to main.
207
208	PR #42 merged ✓
209	Branches cleaned up ✓
210	Version: 1.1.0 → 1.2.0
211
212	Nice work!
213	```
214
215	## Rationalizations to Resist
216
217	Agents under pressure find excuses. These are all violations:
218
219	\| Excuse \| Reality

People who liked this also viewed

6 picks

Type