describe-pr
Generate comprehensive PR descriptions following repository templates
npx skills add parcadei/Continuous-Claude-v3 --skill describe_pr --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Generate PR Description You are tasked with generating a comprehensive pull request description following the repository's standard template. ## Steps to follow: 1. **Read the PR description template:** - First, check if `thoughts/shared/pr_description.md` exists - If it doesn't exist, inform the user they need to create a PR description template at `thoughts/shared/pr_description.md` - Read the template carefully to understand all sections and requirements 2. **Identify the PR to describe:** - Check if the current branch has an associated PR: `gh pr view --json url,number,title,state 2>/dev/null` - If no PR exists for the current branch, or if on main/master, list open PRs: `gh pr list --limit 10 --json number,title,headRefName,author` - Ask the user which PR they want to describe 3. **Check for existing description:** - Check if `thoughts/shared/prs/{number}_description.md` already exists - If it exists, read it and inform the user you'll be updating it - Consider what has changed since the last description was written 4. **Gather comprehensive PR information:** - Get the full PR diff: `gh pr diff {number}` - If you get an error about no default remote repository, instruct the
- Steps to follow:
- Important notes:
What does the describe-pr skill do?
Generate comprehensive PR descriptions following repository templates
How do I install it?
Run `npx skills add parcadei/Continuous-Claude-v3 --skill describe_pr --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From parcadei/Continuous-Claude-v3, a repository with 3,879 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.