本文へ移動
cccskills
無料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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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.

日本語の概要は準備中です。原文の説明を表示しています。

divinevideo/divine-mobile2662026年10月12日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

divinevideo/divine-mobile2662026年10月12日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

divinevideo/divine-mobile2662026年10月12日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

divinevideo/divine-mobile2662026年10月12日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

divinevideo/divine-mobile2662026年10月12日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

divinevideo/divine-mobile2662026年10月12日 更新

divinevideo のスキルをすべて見る

このスキルの問題を報告する