Push branch and open a PR (assigned to @me, labeled, Closes #N)
Scanned 9/12/2026
Install to Claude Code
Skills Directorynpx -y skills add phel-lang/phel-pdo --skill pr --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Pr?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/phel-lang-phel-pdo)More formats (shields.io, HTML) on the badges page.
---
description: Push branch and open a PR (assigned to @me, labeled, Closes #N)
argument-hint: "[issue-number]"
disable-model-invocation: true
allowed-tools: "Read, Edit, Bash(git *), Bash(gh *)"
---
# PR
## Context
!`git branch --show-current`
!`git log main..HEAD --oneline`
## Instructions
1. If `## [Unreleased]` in `CHANGELOG.md` wasn't updated, update it and commit: `docs: update changelog`.
2. `git push -u origin HEAD`.
3. Title: `<type>(<scope>): <short>` (conventional, under 70 chars). Derive type from branch prefix (`feat/` → `feat`, `fix/` → `fix`, `docs/` → `docs`, `ref/` → `ref`). If `$ARGUMENTS` is an issue number, pull the title via `gh issue view <num> --json title -q '.title'`.
4. Pick one label: `bug` (`fix/`), `enhancement` (`feat/`), `documentation` (`docs/`), `refactoring`, `pure testing`, `dependencies`.
5. Open:
```bash
gh pr create --title "<title>" --assignee @me --label "<label>" --body "$(cat <<'EOF'
## Summary
- <what + why, one or two bullets>
## Test plan
- [ ] `composer test` green locally
- [ ] CI green
Closes #<issue-number>
EOF
)"
```
Drop the `Closes` line if there's no linked issue. Body under 15 lines.
6. Report URL.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
