- Use the
ghCLI (gh pr create) for consistency and proper context management. - To keep branch names organized and recognizable, follow the branch naming convention:
type/issue-number-slugortype/slug(e.g.,feat/123-add-login,fix/memory-leak). Valid types includefeat,fix,docs,refactor,chore. - PR titles should follow the Conventional Commits format (e.g.,
feat(auth): add OAuth2 login) to ensure our changelogs and versioning remain accurate. - IMPORTANT: Read and apply the PR template at
.github/pull_request_template.mdif it exists. Structuring the PR body to align with the template makes it easier for reviewers to understand your changes.
create-pull-request
Create a GitHub pull request following project conventions. Use when the user asks to create a PR, submit changes for review, or open a pull request. Handles commit analysis, branch management, and PR creation using the gh CLI tool.
Safety Notice
This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.
Copy this and send it to your AI assistant to learn
Install skill "create-pull-request" with this command: npx skills add hrdtbs/agent-skills/hrdtbs-agent-skills-create-pull-request
Source Transparency
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related Skills
Related by shared tags or category signals.
plan-self-review
No summary provided by upstream source.
commit
No summary provided by upstream source.
Planning with files
Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when aske...