Skip to content

gpsaggese/helpers / .claude/skills/github.find_name_for_pr

github.find_name_for_pr

Verified

Find a title and a description for the current Pull Request

FileKindSize
SKILL.mdskill md3.1 KB
---
description: Find a title and a description for the current Pull Request
model: haiku
---

# Goal
- Given the current Git branch, find a title and a short description to push the
  changes as a Pull Request

# Workflow

## Read Rules

- Read rules about:
  - **Coding**: `.claude/skills/coding.rules.md`
  - **Unit tests**: `.claude/skills/testing.rules.md`

## Read the Changes in the Current Git Client

- Get the changed files:
  ```bash
  git diff --name-status origin/master HEAD
  ...
  ```

- Analyze the diff against `master` (or `origin/master`):
  ```bash
  git diff master...HEAD --name-only
  # or if master is not available locally:
  git diff origin/master...HEAD --name-only
  ```

## Propose the Description of the PR
- Propose a one-line title for the PR
  - It must be Linux friendly: no `&` or non-alphanumeric chars
- Save it into `pr_title.txt`

## Propose the Description of the PR
- Write `pr_commit_msg.txt` with a short list of changes in the format
  ```
  ## <Description of the change>
  - Change1
  - Change2
  ```
  where each `<ChangeN>` is a one or two line bullet describing what changed
  related to `<Description of the change>`
- Use plaintext only, no markdown formatting
- Use nested bullets, not numbered bullets
- Wrap lines under 85 chars

## Write the Description of the PR

- Write `pr_description.md` following the template
  `.claude/templates/github_PR_description.template.md`
- Say in `pr_description.md` how it was generated, with this comment at the top:
  ```markdown
  <!-- Generated by `.claude/skills/github.find_name_for_pr/SKILL.md` -->
  ```
- Fill every section from the diff and from the plan or spec the PR closes
  - Write "N/A: <reason>" for a section that does not apply
  - Do not invent test counts or results: run the tests or ask the user
- Follow `.claude/skills/markdown.rules.md` and `.claude/skills/text.rules.md`

### Example

```
This PR consolidates major infrastructure updates adding developer tools,
standardized documentation templates, and improved onboarding workflows for the
helpers_root ecosystem.

Stats: 192 files changed, 4985 insertions, 2218 deletions

- **Documentation**: Added CONTRIBUTING.md with contribution guidelines and
  task_instructions.md for task execution workflow
- **Figure Creation Skills**: Added 3 new figure-related skills (create_svg, create_tikz,
  make_professional) with rules
- **Templates**: Added github_PR_plan.template.md and architecture_doc.template.md for
  standardized documentation
- **Tooling**: Added scripts for figure compression, image downloading, and git utilities
  (find_junk.sh, git_backup_branch.sh)
- **Onboarding**: Added bounty spam prevention guide for team onboarding
- **Skill Updates**: Improved descriptions and workflows across 120+ skill files with
  consistent formatting
- **Helper Improvements**: Enhanced hdaemon.py and hselect_input_output.py with extended
  functionality
- **Linting**: Updated cc_lint.py with additional linting capabilities
- **Documentation Cleanup**: Removed legacy instr.md and consolidated command rules
```

# Verification

- [ ] The file `pr_description.md` says that it was generated by
      `.claude/skills/github.find_name_for_pr/SKILL.md`
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall