Ship: Build, Install, Commit, Push
SkillDev toolsBuild all packages, reinstall VS Code extension, commit and push. Use when: user says "ship", or wants to build+install+commit+push in one go.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Ship: Build, Install, Commit, Push skill
What this skill tells your AI
The instructions your AI receives, as published by disentinel/grafema in .claude/skills/ship/SKILL.md and read by ahel’s review.
Full pipeline: build all packages, reinstall VS Code extension from source, commit changes, push to remote.
Steps
- Build all packages:
pnpm buildfrom monorepo root - Reinstall VS Code extension: package vsix, install with --force, clean up
- Commit: stage changed files (NOT dist/, NOT .vsix), create commit with user-provided message or auto-generated
- Push:
git pushto current branch remote
Execution
Run these steps sequentially. If any step fails, STOP and report the error.
Step 1: Build
cd /Users/vadimr/grafema && pnpm build
If build fails, stop immediately and show the error.
Step 2: Reinstall VS Code extension
cd /Users/vadimr/grafema/packages/vscode && \
npx vsce package --no-dependencies && \
code --install-extension grafema-explore-*.vsix --force && \
rm grafema-explore-*.vsix
Step 3: Commit
- Run
git statusandgit diff --stagedto see changes - Stage source files only (no dist/, no .vsix, no node_modules)
- If user provided $ARGUMENTS, use it as commit message
- Otherwise, auto-generate a concise commit message from the diff
- Include
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Step 4: Push
git push
Important
- NEVER commit dist/ or .vsix files
- If there are no changes to commit, skip steps 3 and 4
- Always check build output for errors before proceeding
Signals
- GitHub stars
- 36
- Forks
- 3
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
ship-disentinel- Source
- github.com/disentinel/grafema