tim-hub/powerball-harness / .claude/skills/release-this
release-this
VerifiedOrchestrates the full powerball-harness plugin release with build, validation, version bump, CHANGELOG, tag, and GitHub Release. Use when releasing this plugin.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.9 KB |
| references/versioning-rules.md | markdown | 2.5 KB |
| references/writing-changelog.md | markdown | 2.9 KB |
| scripts/bench-residue.shexecutable | script | 1.2 KB |
| scripts/check-consistency.shexecutable | script | 19.7 KB |
| scripts/check-residue.py | script | 16.2 KB |
| scripts/release-preflight.shexecutable | script | 12.2 KB |
| scripts/sync-version.shexecutable | script | 6.6 KB |
| scripts/validate-release-notes.shexecutable | script | 2.4 KB |
references/writing-changelog.md
View on GitHub# CHANGELOG Writing Guide
CHANGELOG entries in this project use a **detailed Before/After format** — each change explains what the user experienced before and what they get after, with concrete examples.
## Quick Reference
| User Input | Subcommand | Behavior |
|------------|------------|----------|
| "Finished a feature / fixed a bug" | `unreleased` | Append to `## [Unreleased]` section |
| "Cutting a release" | `release` | Finalize `[Unreleased]` into a versioned section |
| "Writing GitHub Release notes" | `github-release` | Write English release notes for `gh release create` |
## CHANGELOG Entry Format
### Structure
```markdown
## [X.Y.Z] - YYYY-MM-DD
### Theme: [One-line summary of all changes]
**[Value to users in 1-2 sentences]**
---
#### 1. [Feature Name]
**Before**: [Describe the old behavior concretely — the inconvenience users experienced]
**After**: [Describe the new behavior — what changed and how, with concrete examples]
```
[Actual output or command example]
```
#### 2. [Next Feature Name]
**Before**: ...
**After**: ...
```
### Writing Rules
| Rule | Guidance |
|------|----------|
| Language | **English** |
| Structure | Each feature in its own `#### N. Feature Name` section |
| "Before" | Describes the **pain point** — what users had to do or put up with |
| "After" | Shows the **resolution** — what changes and how, with concrete command/output examples |
| Examples | Always include real command output, Plans.md snippets, or before/after code |
| Detail level | 3–10 lines per feature; readability beats brevity |
| Technical detail | File names and step numbers are supplements in "After", not the headline |
### Preserving `[Unreleased]`
Never empty the `[Unreleased]` section — keep it as a placeholder for the next release:
```markdown
## [Unreleased]
## [X.Y.Z] - YYYY-MM-DD
...
```
## CC Version Integration Pattern
For releases that bundle a new Claude Code version, use the **"CC Update → Harness Usage"** format instead of Before/After. This makes it clear which changes come from upstream CC and which are Harness-specific responses.
See `harness/rules/github-release.md` — "CHANGELOG Pattern for CC Version Integration" for the full template and examples.
## GitHub Release Notes Format
GitHub Releases use **English** and a condensed format with a Before/After table:
```markdown
## What's Changed
**[One-line value description]**
### Before / After
| Before | After |
|--------|-------|
| Previous state | New state |
---
## Added
- **Feature**: Description
## Changed / Fixed
- **Change**: Description
```
Full format rules: `harness/rules/github-release.md`
## Related
- `release-this` skill — Full release workflow (uses this guide at Phase 3)
- `harness/rules/github-release.md` — Detailed GitHub Release format + CC integration pattern
- `harness/rules/versioning.md` — Deciding patch / minor / major
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Unverified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |