PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
A skill your agent uses when running claudikins-kernel:ship, preparing PRs, writing changelogs, deciding merge strategy, or handling CI failures — enforces GRFP-style iterative approval, code…
$ npx skills add povvo/claudikins-kernel --skill shipping-methodology -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install povvo/claudikins-kernel shipping-methodology --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/shipping-methodology .claude/skills/shipping-methodology && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "shipping-methodology" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/shipping-methodology into .claude/skills/shipping-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-methodology", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/povvo/claudikins-kernel/tree/main/skills/shipping-methodologyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add povvo/claudikins-kernel --skill shipping-methodology -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install povvo/claudikins-kernel shipping-methodology --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/shipping-methodology .agents/skills/shipping-methodology && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "shipping-methodology" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/shipping-methodology into .agents/skills/shipping-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-methodology", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add povvo/claudikins-kernel --skill shipping-methodology -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install povvo/claudikins-kernel shipping-methodology --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/shipping-methodology .cursor/skills/shipping-methodology && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "shipping-methodology" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/shipping-methodology into .cursor/skills/shipping-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-methodology", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/povvo/claudikins-kernel.git --path skills/shipping-methodology--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add povvo/claudikins-kernel --skill shipping-methodology -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install povvo/claudikins-kernel shipping-methodology --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/shipping-methodology .gemini/skills/shipping-methodology && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "shipping-methodology" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/shipping-methodology into .gemini/skills/shipping-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-methodology", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install povvo/claudikins-kernel shipping-methodologyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add povvo/claudikins-kernel --skill shipping-methodology -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/shipping-methodology .github/skills/shipping-methodology && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "shipping-methodology" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/shipping-methodology into .github/skills/shipping-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-methodology", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add povvo/claudikins-kernel --skill shipping-methodology -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install povvo/claudikins-kernel shipping-methodology --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/shipping-methodology .opencode/skills/shipping-methodology && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "shipping-methodology" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/shipping-methodology into .opencode/skills/shipping-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-methodology", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
shipping-methodologyA skill your agent uses when running claudikins-kernel:ship, preparing PRs, writing changelogs, deciding merge strategy, or handling CI failures — enforces GRFP-style iterative approval, code…
Shipping Methodology is an agent skill from povvo/claudikins-kernel. 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
Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `references/breaking-change-detection.md`, `references/changelog-merge-strategy.md` and `references/ci-failure-handling.md`).
It sits in Development, covering Changelog and release notes and Failing and flaky tests. The repository describes itself as: SRE thinking applied to Claude Code, based on Boris Cherny's Q&A. It enforces a strict 4-stage pipeline with gates between each step. You literally cannot skip verification. You… The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 8b626a4. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlobBashEditAskUserQuestionSkillmcp__plugin_claudikins-tool-executor_tool-executor__search_toolsmcp__plugin_claudikins-tool-executor_tool-executor__get_tool_schemamcp__plugin_claudikins-tool-executor_tool-executor__execute_codeFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
jqgitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Shipping Methodology loads about 3.2k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 773 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Grep, Glob, Bash, Edit, AskUserQuestion, Skill, mcp__plugin_claudikins-tool-executor_tool-execAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from povvo/claudikins-kernel at commit 8b626a4, republished under its MIT licence (© povvo). 773 words, ~3,215 tokens.
.claude/skills/shipping-methodology/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.Use this skill when you need to:
claudikins-kernel:ship command"Ship with confidence, not hope." - Shipping philosophy
Shipping is the final gate. Apply GRFP-style iterative workflow to every stage.
Show what's being shipped. Human confirms ready.
| Check | What to Show |
|---|---|
| Verification status | All phases PASS from claudikins-kernel:verify |
| Branches to merge | List all execute/task-* branches |
| Evidence summary | Screenshots, curl responses from catastrophiser |
| Code delta | Lines added/removed, files changed |
Checkpoint:
Ready to ship?
Verified: ✓ All checks passed
Branches: 3 branches to merge
Changes: +450 / -120 lines
[Continue] [Back to Verify] [Abort]Draft commit message(s). Human approves.
Decision:
How should we commit?
[Squash into single commit] [Preserve commit history]Squash (recommended for features):
Preserve (for large multi-part work):
Checkpoint:
Commit message:
feat(auth): Add authentication middleware
- JWT token validation
- Role-based access control
- Session management
Closes #42
[Accept] [Revise] [Back]Update README, CHANGELOG, version. GRFP-style.
git-perfectionist uses github-readme plugin:
Files to update:
| File | What to Update |
|---|---|
| README.md | Features, usage, installation if changed |
| CHANGELOG.md | Add entry in Keep a Changelog format |
| package.json / Cargo.toml / pyproject.toml | Version bump if needed |
Checkpoint:
Documentation updates:
README.md:
- Added: Authentication section
- Updated: Installation (new deps)
CHANGELOG.md:
- Added: v1.2.0 entry
Version: 1.1.0 → 1.2.0 (minor)
[Accept] [Revise] [Skip]Draft PR title and body. Section-by-section approval.
PR Title Pattern:
feat(scope): Short descriptionPR Body Structure:
## Summary
[2-3 bullet points of what changed]
## Changes
[Detailed breakdown]
## Testing
[How it was verified]
## Screenshots
[If applicable]Checkpoint:
PR ready to create:
Title: feat(auth): Add authentication middleware
Body:
## Summary
- Added JWT token validation
- Implemented role-based access control
...
[Create PR] [Revise] [Back]CI passes. Human approves. Merge and cleanup.
CI Status Check:
CI Status: ⏳ Running...
[Wait for CI] [View logs] [Merge anyway]On CI pass:
CI Status: ✓ All checks passed
Ready to merge PR #42 to main?
[Merge] [Request review first] [Cancel]After merge:
Final output:
Done! Shipped to main.
PR #42 merged ✓
Branches cleaned up ✓
Version: 1.1.0 → 1.2.0
Nice work!Agents under pressure find excuses. These are all violations:
| Excuse | Reality |
|---|---|
| "Verify passed yesterday, close enough" | Stale verification = no verification. Re-run claudikins-kernel:verify. |
| "Just a tiny fix after verify, no big deal" | Any change after verify invalidates it. Re-run claudikins-kernel:verify. |
| "CI is flaky, I'll merge anyway" | Flaky CI hides real failures. Fix or explicitly skip with caveat. |
| "It's just a typo, skip the PR" | All changes go through PR. No exceptions. |
| "Both reviewers passed, auto-merge is fine" | Human approves final merge. Always. |
| "I'll update the changelog later" | Changelog is part of shipping. Do it now. |
| "Force push is fine, it's my branch" | Never force push to protected branches. Ever. |
| "Skip docs, nobody reads them" | Docs are part of shipping. GRFP them. |
| "The gate check is too strict" | The gate exists for a reason. Pass it properly. |
All of these mean: Follow the methodology. Shortcuts create incidents.
If you're thinking any of these, you're about to violate the methodology:
All of these mean: STOP. Gate check exists. Human decides. Follow the stages.
The ship-init.sh hook enforces the claudikins-kernel:verify gate with code integrity validation.
# 1. Verify state exists
if [ ! -f "$VERIFY_STATE" ]; then
echo "ERROR: claudikins-kernel:verify has not been run"
exit 2
fi
# 2. Unlock flag is set
UNLOCK=$(jq -r '.unlock_ship // false' "$VERIFY_STATE")
if [ "$UNLOCK" != "true" ]; then
echo "ERROR: claudikins-kernel:verify did not pass or was not approved"
exit 2
fiEnsure we ship exactly what was verified:
# C-5: Commit hash validation
VERIFY_COMMIT=$(jq -r '.verified_commit_sha' "$VERIFY_STATE")
CURRENT_COMMIT=$(git rev-parse HEAD)
if [ "$VERIFY_COMMIT" != "$CURRENT_COMMIT" ]; then
echo "ERROR: Code changed since verification"
exit 2
fi
# C-7: File manifest validation
VERIFIED_MANIFEST=$(jq -r '.verified_manifest' "$VERIFY_STATE")
CURRENT_MANIFEST=$(sha256sum "$MANIFEST_FILE" | cut -d' ' -f1)
if [ "$VERIFIED_MANIFEST" != "$CURRENT_MANIFEST" ]; then
echo "ERROR: Source files changed after verification"
exit 2
fiIf integrity check fails:
Code has changed since verification.
Verified commit: abc123
Current commit: def456
[Re-run claudikins-kernel:verify] [Abort]feat(scope): Short description
- Bullet point of what changed
- Another change
Closes #123fix(scope): Short description
Root cause: What was wrong
Fix: What we did
Fixes #456feat(scope)!: Short description
BREAKING CHANGE: What breaks and migration path
- Change 1
- Change 2chore(scope): Short description
- Internal refactor
- Dependency updateSee commit-message-patterns.md for full guide.
Follow Keep a Changelog format:
## [Unreleased]
## [1.2.0] - 2026-01-17
### Added
- Authentication middleware with JWT support (#42)
### Changed
- Updated error messages for clarity
### Fixed
- Token refresh race condition (#38)
## [1.1.0] - 2026-01-10
...See changelog-merge-strategy.md for merging entries.
PR creation failed.
Error: GitHub API returned 503
Retry 1/3...Pattern: Max 3 retries with exponential backoff.
If persistent:
GitHub API unavailable after 3 retries.
[Try again] [Save as draft PR] [Manual merge]Save state with pending_merge: true for recovery.
CI failed.
Failed checks:
- lint: 2 errors
- test: 1 failure
[View logs] [Fix and retry] [Skip CI] [Abort]See ci-failure-handling.md for recovery patterns.
Never force push to protected branches.
# Check if target is protected
PROTECTED_BRANCHES="main master release"
if echo "$PROTECTED_BRANCHES" | grep -q "$TARGET"; then
if [ "$FORCE" = "true" ]; then
echo "ERROR: Cannot force push to $TARGET"
exit 2
fi
fiSee force-push-protection.md for safeguards.
Detect breaking changes before shipping:
| Signal | Indicates |
|---|---|
| Removed public function | Breaking |
| Changed function signature | Breaking |
| Removed config option | Breaking |
| Changed default behaviour | Potentially breaking |
If breaking change detected:
Breaking change detected!
- Removed: authenticate() function
- Changed: login() now requires email
This requires a MAJOR version bump.
[Acknowledge and continue] [Abort]See breaking-change-detection.md for detection patterns.
Don't do these:
{
"session_id": "ship-2026-01-17-1130",
"verify_session_id": "verify-2026-01-17-1100",
"target": "main",
"phases": {
"pre_ship_review": { "status": "APPROVED" },
"commit_strategy": { "status": "APPROVED", "strategy": "squash" },
"documentation": {
"status": "APPROVED",
"files_updated": ["README.md", "CHANGELOG.md"]
},
"pr_creation": { "status": "CREATED", "pr_number": 42 },
"merge": { "status": "MERGED", "sha": "abc123" }
},
"cleanup": {
"branches_deleted": ["execute/task-1-auth", "execute/task-2-routes"]
},
"shipped_at": "2026-01-17T11:46:00Z"
}Full documentation in this skill's references/ folder:
© povvo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 10 other files (references) in skills/shipping-methodology of povvo/claudikins-kernel.
Open the folder on GitHubat commit 8b626a4
Shipping Methodology next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Shipping Methodology this skillpovvo/claudikins-kernel | 128 | — | ~3.2k | Automated safety check: Notes | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| StarRocks Release NotesStarRocks/starrocks | 12k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Systematic Debuggingultralisp/ultralisp | 258 | 51 repos | ~2.4k | Automated safety check: Pass | None |
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
StarRocks/starrocks
Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
povvo/claudikins-kernel
A skill your agent uses when running claudikins-kernel:outline, brainstorming implementation approaches, gathering requirements iteratively, structuring complex technical plans, or facing analysis…
povvo/claudikins-kernel
A skill your agent uses when running claudikins-kernel:execute, decomposing plans into tasks, setting up two-stage review, deciding batch sizes, or handling stuck agents — enforces isolation…
povvo/claudikins-kernel
A skill your agent uses when running claudikins-kernel:verify, checking implementation quality, deciding pass/fail verdicts, or enforcing cross-command gates — requires actual evidence of code…
Categories
A skill your agent uses when running claudikins-kernel:ship, preparing PRs, writing changelogs, deciding merge strategy, or handling CI failures — enforces GRFP-style iterative approval, code…. Shipping Methodology is an agent skill from povvo/claudikins-kernel.
Shipping Methodology fits situations like: running claudikins-kernel:ship; writing changelogs; deciding merge strategy; handling CI failures — enforces GRFP-style iterative approval.
Run `npx skills add povvo/claudikins-kernel --skill shipping-methodology -a claude-code`. Or copy the skill folder (skills/shipping-methodology in povvo/claudikins-kernel) into .claude/skills/shipping-methodology in your project. Claude Code loads it when a task matches its description.
Run `npx skills add povvo/claudikins-kernel --skill shipping-methodology -a codex`. Or copy the skill folder (skills/shipping-methodology in povvo/claudikins-kernel) into .agents/skills/shipping-methodology in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add povvo/claudikins-kernel --skill shipping-methodology -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/shipping-methodology, .gemini/skills/shipping-methodology, .github/skills/shipping-methodology and .opencode/skills/shipping-methodology in your project.
Going by SKILL.md and its folder, Shipping Methodology needs the command-line tools its instructions call (jq and git). Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash, Edit, AskUserQuestion, Skill, mcp__plugin_claudikins-tool-executor_tool-executor__search_tools, mcp__plugin_claudikins-tool-executor_tool-executor__get_tool_schema, mcp__plugin_claudikins-tool-executor_tool-executor__execute_code.
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Shipping Methodology is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 14k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Shipping Methodology: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars) and Cutting A Release (TriliumNext/Trilium, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
povvo (a GitHub user) maintains it in povvo/claudikins-kernel, which has 128 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on April 22, 2026.
Source: povvo/claudikins-kernel on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.