npx claudepluginhub jezweb/claude-skills --plugin dev-toolsThis skill uses the workspace's default tool permissions.
Sanitize and release projects to GitHub. Two-phase workflow: safety checks first, then tag and publish.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Sanitize and release projects to GitHub. Two-phase workflow: safety checks first, then tag and publish.
gh CLI installed and authenticated (gh auth status)gitleaks installed for secrets scanning (brew install gitleaks or download from GitHub)Run these checks before any public release. Stop on blockers.
gitleaks detect --no-git --source=. --verbose
If secrets found: STOP. Remove secrets, move to environment variables. Check git history with git log -S "secret_value" — if in history, use BFG Repo-Cleaner.
If gitleaks not installed, do manual checks:
# Check for .env files
find . -name ".env*" -not -path "*/node_modules/*"
# Check config files for hardcoded secrets
grep -ri "api_key\|token\|secret\|password" wrangler.toml wrangler.jsonc .dev.vars 2>/dev/null
Check for and remove session/planning files that shouldn't be published:
SESSION.md — session stateplanning/, screenshots/ — working directoriestest-*.ts, test-*.js — local test filesEither delete them or add to .gitignore.
ls LICENSE LICENSE.md LICENSE.txt 2>/dev/null
If missing: create one. Check the repo visibility (gh repo view --json visibility -q '.visibility'). Use MIT for public repos. For private repos, consider a proprietary license instead.
Check README exists and has basic sections:
grep -i "## Install\|## Usage\|## License" README.md
If missing sections, add them before release.
Verify essential patterns are present:
grep -E "node_modules|\.env|dist/|\.dev\.vars" .gitignore
npm run build 2>&1
npm audit --audit-level=high
If any changes were made during sanitization:
git add -A
git commit -m "chore: prepare for release"
Check package.json for current version, or ask the user. Ensure version starts with v prefix.
git tag -l "v[version]"
If it exists, ask user whether to delete and recreate or use a different version.
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
if [ -z "$LAST_TAG" ]; then
git log --oneline --no-merges HEAD | head -20
else
git log --oneline --no-merges ${LAST_TAG}..HEAD
fi
git tag -a v[version] -m "Release v[version]"
git push origin $(git branch --show-current)
git push origin --tags
gh release create v[version] \
--title "Release v[version]" \
--notes "[auto-generated from commits]"
For pre-releases add --prerelease. For drafts add --draft.
Show the user:
| When | Read |
|---|---|
| Detailed safety checks | references/safety-checklist.md |
| Release mechanics | references/release-workflow.md |