AgentStack
SKILL verified MIT Self-run

Github Pr

skill-dhruvanbhalara-skills-github-pr · by dhruvanbhalara

Automate Pull Request creation with proper titles, descriptions, labels, and quality checks using the GitHub CLI. Use when preparing code for review and merge.

No reviews yet
0 installs
14 views
0.0% view→install

Install

$ agentstack add skill-dhruvanbhalara-skills-github-pr

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Github Pr? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Pull Request Creation & Management

This skill automates the process of creating high-quality Pull Requests using the GitHub CLI (gh) or providing instructions if it's unavailable.

1. Preparation

  • Check GitHub CLI: Verify if gh is installed and authenticated (gh auth status).
  • Commits Check: Ensure all changes are committed in the current feature branch.
  • Base Branch: Identify the target base branch (usually main).

2. PR Quality & Metadata

  • Quality Gate: All PRs MUST pass analysis (0 warnings), formatting, and tests before merge.
  • Branch Protection: Ensure branch protection rules are respected (no direct pushes to main).
  • Metadata: ALWAYS specify relevant labels and at least one assignee.
  • Checklist: Ensure the development plan and requirements are reviewed before completing the task.

3. Generate PR Title

  • Conventional Commits: The PR title MUST follow the pattern: (): .
  • Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert.
  • Example: feat(auth): add google sign-in support
  • Source: Analyze the commit messages in the current branch to determine the most appropriate title.

3. Generate PR Description

  • Commit History: Read all commits in the current branch (git log origin/main..HEAD --oneline).
  • PR Template: Check for .github/PULL_REQUEST_TEMPLATE.md or similar. If it exists, populate it.
  • Content:
  • Summarize the "What" and "Why" of the changes.
  • List the specific changes as bullet points.
  • Include any relevant issue numbers (e.g., Closes #123).

4. Labeling & Assignment

  • Available Labels: Fetch labels from the repo (gh label list).
  • Auto-Label: Assign labels based on the changes:
  • enhancement / feat: For new features.
  • bug / fix: For bug fixes.
  • documentation / docs: For documentation updates.
  • Assignee: Assign the PR to the current user or as per project rules.

5. Execution

  • Using CLI: If gh is available, run:

``bash gh pr create --title "" --body "" --label "" ``

  • Manual Fallback: If gh is NOT available, present the generated title, description, and suggested labels to the user and ask how to proceed.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.