Docs & Writing vs Testing · both proven

changelog-generator vs receiving-code-review

Both skills were run through Claude twice: once on a fixed brief without the skill, once with it. The briefs differ because each is written for the job the skill claims to do, so compare each skill against its own baseline, then decide which difference matters for your work. They are in different categories, so this is a choice of job, not a head-to-head on the same job.

changelog-generator

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Category: Docs & Writing
Source: ComposioHQ/awesome-claude-skills
License: Not stated
Proof model: claude-opus-5-5
Brief: “Turn these git commits into a user-facing changelog page for version 2.4.0 of Ledgerly, a small-business invoicing app, as a single HTML page. Commits: 'feat: recurring invoices with weekly, monthly and custom schedules'; 'feat: export invoices to CSV from the list view'; 'fix: PDF totals rounded incorrectly for invoices with more than 50 line items'; 'fix: late-fee reminder emails sent twice when a client had two contacts'; 'chore: bump node to 22'; 'refactor: move tax calculation into shared module'; 'feat: Stripe payouts show in the dashboard with a status badge'; 'fix: dark mode contrast on the settings page'; 'docs: update API examples for the invoices endpoint'.”
Skill commit: be2a406

Without the skillWith changelog-generator

⇆

Without, runWith changelog-generator, run3 independent runs per side, none selected by hand.

Download the with-skill page

receiving-code-review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Category: Testing
Source: obra/superpowers
License: MIT
Proof model: claude-opus-5-5
Brief: “I received this code review on my pull request that adds caching to our product API. Decide what to do with each comment and present your responses and planned changes as a single HTML page. 1. "Cache TTL of 24h is too long, prices change during the day." 2. "Use Redis instead of the in-memory Map so all 4 instances share the cache." 3. "Rename getProd to getProduct." 4. "You should rewrite this whole module in TypeScript." 5. "The cache key ignores the currency query param, so EUR users can get USD prices." 6. "Add a test."”
Skill commit: 2ce8aa1

Without the skillWith receiving-code-review

⇆

Without, runWith receiving-code-review, run3 independent runs per side, none selected by hand.

Download the with-skill page

We don’t pick a winner for you: the pages are the evidence. Both proofs can be repeated with the brief, model and commit shown above. See alternatives to changelog-generator or alternatives to receiving-code-review.