comprehensive-review-pr-enhance
Generate structured PR descriptions from diffs, add review checklists, risk assessments, and test coverage summaries. Use when the user says "write a PR description", "improve this PR", "summarize my changes", "PR review", "pull request", or asks to document a diff for reviewers.
What this skill does
# Pull Request Enhancement ## When to Use - You need to turn a git diff into a reviewer-friendly pull request description. - You want a PR summary with change categories, risks, testing notes, and a checklist. - The diff is large enough that reviewers need explicit structure instead of a short ad hoc summary. ## Workflow 1. Run `git diff <base>...HEAD --stat` to identify changed files and scope 2. Categorise changes: source, test, config, docs, build, styles 3. Generate the PR description using the template below 4. Add a review checklist based on which file categories changed 5. Flag breaking changes, security-sensitive files, or large diffs (>500 lines) ## PR Description Template ```markdown ## Summary <!-- one-paragraph executive summary: what changed and why --> ## Changes | Category | Files | Key change | |----------|-------|------------| | source | `src/auth.ts` | added OAuth2 PKCE flow | | test | `tests/auth.test.ts` | covers token refresh edge case | | config | `.env.example` | new `OAUTH_CLIENT_ID` var | ## Why <!-- link to issue/ticket + one sentence on motivation --> ## Testing - [ ] unit tests pass (`npm test`) - [ ] manual smoke test on staging - [ ] no coverage regression ## Risks & Rollback - **Breaking?** yes / no - **Rollback**: revert this commit; no migration needed - **Risk level**: low / medium / high — because ___ ``` ## Review Checklist Rules Add checklist sections only when the matching file category appears in the diff: | File category | Checklist items | |---------------|----------------| | source | no debug statements, functions <50 lines, descriptive names, error handling | | test | meaningful assertions, edge cases, no flaky tests, AAA pattern | | config | no hardcoded secrets, env vars documented, backwards compatible | | docs | accurate, examples included, changelog updated | | security-sensitive (`auth`, `crypto`, `token`, `password` in path) | input validation, no secrets in logs, authz correct | ## Splitting Large PRs When diff exceeds 20 files or 1000 lines, suggest splitting by feature area: ``` git checkout -b feature/part-1 git cherry-pick <commits-for-part-1> ``` ## Resources - `resources/implementation-playbook.md` — Python helpers for automated PR analysis, coverage reports, and risk scoring ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.