agentskills.codes
FF

ff_describe_pr

by redblacktreeWritingSource

Creates automated, structured PR descriptions from branch context.

GitDocumentation

Install

mkdir -p .claude/skills/ff-describe-pr && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13052" && unzip -o skill.zip -d .claude/skills/ff-describe-pr && rm skill.zip

Installs to .claude/skills/ff-describe-pr

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Create or update a pull request description from local diff and GitHub metadata
79 charsno explicit “when” trigger
Beginner

Key capabilities

  • →Identify the pull request.
  • →Find a template for the PR description.
  • →Gather evidence from git status, log, and diff.
  • →Write a concise PR body to a file.
  • →Update an existing PR with the body file.
  • →Print the PR URL, body file path, and verification.

How it works

The skill identifies the PR, finds a template, gathers git evidence, writes a PR body to a file, and then updates the PR on GitHub using `gh pr edit`.

Inputs & outputs

You give it
Local diff and GitHub metadata.
You get back
A concise PR description file and an updated pull request on GitHub.

When to use ff_describe_pr

  • →Generate PR summary
  • →Update PR description
  • →Create PR change log

About this skill

Describe Pull Request

Generate a useful PR description from the current branch, local diff, commits, tests, and any repository template. Use gh when available and authenticated. Do not assume a thoughts-specific template exists.

Process

  1. Identify the PR:
    • Try gh pr view --json url,number,title,state,baseRefName,headRefName.
    • If there is no PR yet, use the current branch and commit range against the default branch.
  2. Find a template, in this order:
    • .github/pull_request_template.md
    • .github/PULL_REQUEST_TEMPLATE.md
    • thoughts/shared/pr_description.md
    • Otherwise use the default format below.
  3. Gather evidence:
    • git status
    • git log --oneline origin/main..HEAD or the appropriate base branch
    • git diff --stat and relevant diffs
    • verification commands already run in this session, or run obvious safe checks if needed
  4. Write a concise PR body to thoughts/shared/prs/{number-or-branch}_description.md when that directory exists, otherwise write pr_description.md in the repository root.
  5. If a PR exists, update it with gh pr edit --body-file <file>.

Default PR Format

## Summary
- {change 1}
- {change 2}

## Why
{problem or goal}

## Verification
- [x] `command` - {result}
- [ ] Manual: {manual check still needed}

## Risks / Notes
- {risk, migration note, or follow-up}

Completion

Print the PR URL if available, the body file path, and any verification that still needs human attention.

When not to use it

  • →When a useful PR description is not needed.
  • →When a thoughts-specific template is assumed to exist.
  • →When gh is not available or authenticated.

Limitations

  • →It does not assume a thoughts-specific template exists.
  • →It requires `gh` to be available and authenticated for updating PRs.
  • →It uses a default format if no template is found.

How it compares

This skill automates the generation and update of a PR description by use local git state and repository templates, providing a structured and consistent approach compared to manually writing each PR description.

Compared to similar skills

ff_describe_pr side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
ff_describe_pr (this skill)03moNo flagsBeginner
prepare-changelog67moReviewBeginner
workthrough108moReviewBeginner
generate-release-notes78moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

prepare-changelog

nextest-rs

Guidelines for preparing changelog entries for nextest releases following Keep a Changelog format

689

workthrough

bear2u

Automatically document all development work and code modifications in a structured workthrough format. Use this skill after completing any development task, bug fix, feature implementation, or code refactoring to create comprehensive documentation.

1085

generate-release-notes

teambit

Generate comprehensive release notes for Bit from git commits and pull requests. Use when creating release notes, building changelogs, documenting version releases, or preparing a new Bit release.

752

changelog-generator

ComposioHQ

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.

346

release-note-generation

microsoft

Toolkit for generating PowerToys release notes from GitHub milestone PRs or commit ranges. Use when asked to create release notes, summarize milestone PRs, generate changelog, prepare release documentation, request Copilot reviews for PRs, update README for a new release, manage PR milestones, or collect PRs between commits/tags. Supports PR collection by milestone or commit range, milestone assignment, grouping by label, summarization with external contributor attribution, and README version bumping.

537

doc-check

coder

Checks if code changes require documentation updates

427

Search skills

Search the agent skills registry