Skip to content

tim-hub/powerball-harness / .claude/skills/release-this

release-this

Verified

Orchestrates the full powerball-harness plugin release with build, validation, version bump, CHANGELOG, tag, and GitHub Release. Use when releasing this plugin.

FileKindSize
SKILL.mdskill md6.9 KB
references/versioning-rules.mdmarkdown2.5 KB
references/writing-changelog.mdmarkdown2.9 KB
scripts/bench-residue.shexecutablescript1.2 KB
scripts/check-consistency.shexecutablescript19.7 KB
scripts/check-residue.pyscript16.2 KB
scripts/release-preflight.shexecutablescript12.2 KB
scripts/sync-version.shexecutablescript6.6 KB
scripts/validate-release-notes.shexecutablescript2.4 KB

scripts/validate-release-notes.sh

View on GitHub
#!/bin/bash
# validate-release-notes.sh
# GitHub Release notes format validation script
# Usage: ./scripts/validate-release-notes.sh [tag]
# Example: ./scripts/validate-release-notes.sh v2.10.0

set -e

TAG="${1:-}"
ERRORS=0

# Color definitions
RED='\033[0;31m'
GREEN='\033[0;32m'
YELLOW='\033[1;33m'
NC='\033[0m' # No Color

log_error() {
    echo -e "${RED}❌ $1${NC}"
    ERRORS=$((ERRORS + 1))
}

log_warn() {
    echo -e "${YELLOW}⚠️  $1${NC}"
}

log_ok() {
    echo -e "${GREEN}✅ $1${NC}"
}

# If no tag is specified, check the latest release
if [ -z "$TAG" ]; then
    TAG=$(gh release list --limit 1 --json tagName -q '.[0].tagName')
    echo "📋 Checking latest release: $TAG"
fi

# Get release notes
NOTES=$(gh release view "$TAG" --json body -q '.body' 2>/dev/null)

if [ -z "$NOTES" ]; then
    log_error "Release not found: $TAG"
    exit 1
fi

echo ""
echo "🔍 Release notes validation: $TAG"
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
echo ""

# 1. Heading check
if echo "$NOTES" | grep -qE "^## (What's Changed|What's New|Summary)"; then
    log_ok "Heading: present"
else
    log_error "Missing heading: ## What's Changed"
fi

# 2. Before / After table check
if echo "$NOTES" | grep -qE "Before.*(→|/|\\|).*After"; then
    log_ok "Before / After table: present"
else
    log_error "Before / After table is missing"
fi

# 3. Footer check
if echo "$NOTES" | grep -q "Generated with \[Claude Code\]"; then
    log_ok "Footer: present"
else
    log_warn "Footer not found (recommended: '🤖 Generated with [Claude Code](...)')"
fi

# 4. Section check
for section in "Added" "Changed" "Fixed" "Security"; do
    if echo "$NOTES" | grep -q "^## $section"; then
        log_ok "Section: $section present"
    fi
done

# 6. Bold summary check
if echo "$NOTES" | head -10 | grep -qE "^\*\*.+\*\*$"; then
    log_ok "Bold summary: present"
else
    log_warn "Bold summary not found (describe the value of the change in one line)"
fi

echo ""
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"

if [ $ERRORS -gt 0 ]; then
    echo -e "${RED}Validation result: $ERRORS error(s)${NC}"
    echo ""
    echo "📖 Reference: harness/rules/github-release.md"
    exit 1
else
    echo -e "${GREEN}Validation result: all checks passed${NC}"
    exit 0
fi
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall