codemie-pr

Automate git commit, push, and GitHub PR creation with conventional commits.

267|70|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/codemie-ai/codemie-code --skill codemie-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codemie-pr
Source: https://github.com/codemie-ai/codemie-code/tree/main/.claude/skills/codemie-pr
Command: npx skills add https://github.com/codemie-ai/codemie-code --skill codemie-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates git commit, push, and GitHub PR workflows, ensuring conventional commit messages and preventing duplicate PRs, streamlining collaboration.

Core Features & Use Cases

  • Automated commit workflow: commits with a conventional message format in response to user requests such as "commit changes".
  • Push and PR creation: pushes on the current branch and creates a PR via GitHub CLI when requested, avoiding duplicates.
  • Branch-awareness: automatically handles feature branches when not on main and checks for existing PRs before creation.

Quick Start

Say "commit changes" to perform a commit with a conventional message:

  • git add .
  • git commit -m "<type>(<scope>): <description>"

Say "push changes" to push the current branch:

  • git push origin $(git branch --show-current)

Say "create PR" to push changes and open a PR using the repository's PR template:

  • gh pr create --title "<type>(<scope>): brief description" --body "$(cat .github/PULL_REQUEST_TEMPLATE.md 2>/dev/null || echo 'PR details here')"

Frequently Asked Questions about codemie-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git commits with conventional commit messages?

Automating git commits with conventional commit messages requires running a workflow that stages changes and applies a formatted commit message like "<type>(<scope>): <description>". This Skill handles that process automatically when you request a commit.

Can I create a GitHub pull request using the gh CLI without making duplicates?

Creating a GitHub pull request with the gh CLI without duplicates requires checking for existing PRs on the current branch before creation. This Skill performs that branch-aware check and uses the repository's PR template to open a new PR safely.

Do I need the GitHub CLI installed to automate push and PR workflows?

You need the GitHub CLI (gh) installed and available in PATH to automate push and PR workflows. Git must also be installed, as this Skill relies on both tools to execute branch checks, pushes, and conventional commit processes.

How does branch-awareness prevent duplicate pull requests in feature-branch workflows?

Branch-awareness prevents duplicate pull requests by automatically checking if a PR already exists for the current feature branch before creating a new one. This ensures streamlined collaboration in software projects using feature-branch workflows.

What is the best way to push changes to a remote feature branch automatically?

Pushing changes to a remote feature branch automatically involves executing a git push command targeting the current branch. This Skill automates this by running git push origin on the active branch name when you request to push changes.

Does automated PR creation work with an existing PULL_REQUEST_TEMPLATE.md file?

Automated PR creation works with an existing PULL_REQUEST_TEMPLATE.md file by reading the template content and applying it to the PR body. If the template is missing, it falls back to a default text string for the PR details.