Skip to content

borghei/Claude-Skills / engineering/pr-description-writer

pr-description-writer

Verified

Write PR descriptions with evidence, verification steps and a one-way/two-way merge-risk call. Use when opening a PR, when asked to write or fix a PR body, or when checking a description before requesting review.

assets/sample_changed_files.json

View on GitHub
{
  "description": "Changed paths for the sample PR (git diff --name-only main...HEAD). Includes a schema migration, so the honest classification is one-way.",
  "files": [
    "db/migrations/20261102_split_customer_name.py",
    "app/customers/models.py",
    "app/customers/serializers.py",
    "app/customers/views.py",
    "api/openapi.yaml",
    "tests/customers/test_name_split.py",
    "docs/changelog.md"
  ]
}
receiving-code-reviewobra/superpowersUse 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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall