Skip to content
cccskills
FreePublished on GitHub

pr-summary

Generate a PR description following the project's pull_request_template.md. Analyzes all commits on the current branch vs main, summarizes changes, and outputs a ready-to-paste PR body. Invoke with /pr-summary.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile
See how to install

Files included (1)

  • SKILL.md3.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

PR Summary Skill

Purpose

Generate a pull request description that follows the project's .github/pull_request_template.md format. Analyzes all changes on the current branch compared to main and produces a concise, ready-to-paste PR body.

Workflow

Step 1: Gather Context

# Current branch name
git branch --show-current

# Commits on this branch vs main
git log main..HEAD --oneline

# Files changed with stats
git diff main...HEAD --stat

# Full diff for analysis
git diff main...HEAD

Step 2: Detect Issue Number

Look for the related issue number from (in priority order):

  1. Argument passed to the skill
  2. Branch name (e.g., fix/explore-hashtags-empty-view -> search issues)
  3. Commit messages (e.g., Closes #1461)

Step 3: Analyze Changes

Read the diff and identify:

  • What the change does (1-3 sentences max)
  • Which type of change it is (bug fix, feature, refactor, etc.)
  • Key architectural decisions (layers affected, new files, patterns used)

Step 4: Output

Output the PR body as a raw markdown code block so the user can copy-paste it directly into the GitHub PR description field.

Wrap the entire output in a fenced code block with the markdown language tag:

```markdown
<the PR body here>
```

Output Template

The content inside the code block must follow this structure exactly:

## Description

[1-3 sentence summary of what changed and why]

**Related Issue:** Closes #[number]

## Type of Change

- [ ] New feature (non-breaking change which adds functionality)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
- [ ] Code refactor
- [ ] Build configuration change
- [ ] Documentation
- [ ] Chore

Only check the applicable type ([x]). Keep the description short and focused on the "what" and "why", not implementation details. Reviewers can read the diff for the "how".

Rules

  • Output as code block: Always wrap the full PR body in a ```markdown fenced code block so the user can copy-paste directly into GitHub.
  • Be concise: 1-3 sentences for description. No implementation details.
  • Follow the template exactly: Use the checkboxes from pull_request_template.md.
  • Single type: Only check one type of change unless it genuinely spans multiple.
  • Link the issue: Always include Closes #N if an issue is known.
  • No emoji in description: The template already has emoji in the type checkboxes.
  • No file lists or tables: The diff is available for reviewers. Don't duplicate it.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

argocd-externalsecret-namespace-permission

Free

Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y". Use when: (1) ExternalSecret shows OutOfSync in ArgoCD but won't sync, (2) ArgoCD application status shows "namespace X is not permitted in project 'infrastructure'", (3) ExternalSecret targets a namespace managed by a different ArgoCD project, (4) Using apps-of-apps pattern with separate infrastructure and application projects.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile266Updated Oct 19, 2026

art-direct

Free

Art direction for any content — reads text, PDF, Word, HTML, PPT, then proposes 2-3 creative directions with photography style, mood, and visual language. After selection, generates AI image prompts and visual briefs section-by-section. Use when the user shares content and needs visual direction, image sourcing, or creative direction for any material.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile266Updated Oct 19, 2026

async-await-null-race-condition

Free

Fix "Null check operator used on a null value" errors when an object is set to null during an async await. Use when: (1) Object reference is nullified while awaiting, (2) Code accesses object with ! after await returns, (3) Cancel/dispose operations run concurrently with async operations on same object. Solution: capture local reference before await.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile266Updated Oct 19, 2026

aws-v4-signing-custom-headers-gcs

Free

Add custom metadata headers (x-amz-meta-*) to AWS v4 signed requests for GCS S3-compatible API. Use when: (1) Adding custom metadata to GCS uploads via S3 API, (2) Getting signature mismatch errors after adding new headers, (3) x-amz-meta-* headers being ignored or causing 403 errors. Custom headers MUST be included in canonical headers and signed headers list.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile266Updated Oct 19, 2026

bash-herestring-newline-secrets

Free

Fix password/secret authentication failures caused by trailing newlines when creating Google Cloud secrets (or similar) with bash here-strings. Use when: (1) Password authentication fails with correct password, (2) Secret created with `<<< "value"` syntax, (3) Error like "password authentication failed" or "invalid token" despite correct value. Bash here-strings (`<<<`) add a trailing newline that corrupts secrets.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile266Updated Oct 19, 2026

blossom-content-addressed-url-filtering

Free

Fix silent video/media processing failures caused by URL extraction code that filters on file extensions (.mp4, .webm, .webp). Use when: (1) Media moderation, transcoding, or analysis silently skips files from Blossom or content-addressed storage servers, (2) URL extraction from Nostr event tags (imeta, r tags) drops URLs without recognized extensions, (3) CDN fallback URLs append .mp4 but the actual server uses extensionless content-addressed paths like /{sha256}. Common in Nostr video events (kind 34236) where different clients use different URL formats.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile266Updated Oct 19, 2026

See all skills by divinevideo

Report a problem with this skill