Create GitHub Pull Requests with conventional commit titles and structured descriptions.
npx skills add https://github.com/statick88/dotfiles --skill github-pr-statick88
Please help me install this Agent Skill. Skill: github-pr Source: https://github.com/statick88/dotfiles/tree/main/amp/.agents/skills/github-pr Command: npx skills add https://github.com/statick88/dotfiles --skill github-pr-statick88
This Skill helps you create high-quality GitHub Pull Requests by adhering to conventional commit standards and structuring your descriptions effectively, making reviews smoother and code more maintainable.
feat(scope): description).gh CLI for creating PRs with titles, bodies, reviewers, and labels.feat(user): implement profile editing and a detailed body explaining the changes and how to test them.Use the github-pr skill to create a pull request with the title "feat(auth): add password reset" and a body explaining the changes.
High-intent search queries and answers about installing and using this skill.
To create a GitHub pull request with conventional commit formats, structure your PR title using prefixes like `feat(scope): description` and use the `gh` CLI to generate the PR with a detailed body, reviewers, and labels.
A well-structured pull request description should include a clear summary of changes, a breakdown of what was modified, and testing information so reviewers can verify the code effectively.
Yes, you can use the GitHub CLI to automate pull request creation by specifying titles, bodies, reviewers, and labels in the command, ensuring atomic commits and clear communication in your workflow.
Pull requests often get rejected during code review due to unclear communication or non-atomic commits. Enforcing conventional commit standards and providing structured descriptions makes reviews smoother and code more maintainable.
Yes, you need the GitHub CLI installed to automate pull request generation, as this approach relies on `gh` commands for specifying titles, bodies, reviewers, and labels directly from your terminal.
The best way to format PR titles for feature additions is using the conventional commit standard, such as `feat(user): implement profile editing`, which scopes the change and clarifies the intent for reviewers.
tc9011Verify tests, then merge locally, create a GitHub Pull Request, or preserve the branch.
EdanStarfireCreate, monitor, and merge GitHub pull requests with validation and cleanup.
drgaciwGenerate changelogs and release notes from Conventional Commits in CI/CD pipelines.
StudyDriftClean noisy PR history and add reviewer guidance without altering code behavior.