playbooks

home / skills / codyswanngt / lisa / git-commit-and-submit-pr

git-commit-and-submit-pr skill

/.claude/skills/git-commit-and-submit-pr

This skill creates conventional commits for changes and submits a pull request for review by executing git-commit and git-submit-pr.

npx playbooks add skill codyswanngt/lisa --skill git-commit-and-submit-pr

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
371 B
---
name: git-commit-and-submit-pr
description: This skill should be used when creating conventional commits for current changes and then submitting the current branch as a pull request for code review. It combines the git:commit and git:submit-pr skills into a single workflow.
allowed-tools: ["Bash"]
---

1. Run /git-commit $ARGUMENTS
2. Run /git-submit-pr $ARGUMENTS

Overview

This skill automates creating a conventional commit for your current changes and then submits the current branch as a pull request for code review. It bundles the commit and PR submission steps into a single, consistent workflow to reduce context switching. Use it to enforce commit message style and speed up the review handoff.

How this skill works

The skill first runs the commit step, prompting or using provided arguments to generate a conventional commit message and create the commit. After the commit completes, it runs the PR submission step to push the branch and open a pull request with the composed title and description. It accepts the same arguments you would pass to the individual commit and submit-pr commands and sequences them reliably.

When to use it

  • You have staged changes and want to create a conventional commit and open a PR in one action.
  • You want to enforce consistent commit messages before requesting review.
  • You are finishing a feature or bugfix and need to push and request review quickly.
  • You prefer a single command that handles commit creation and PR submission together.
  • You want to reduce errors from forgetting to push or open a PR after committing.

Best practices

  • Write clear, conventional commit messages that summarize intent and scope.
  • Stage only related changes before running the skill to keep commits focused.
  • Provide explicit arguments for PR title and description to avoid generic defaults.
  • Run tests and linters locally before committing to minimize failed CI on PRs.
  • Confirm branch naming follows team conventions to keep the repo organized.

Example use cases

  • Finish a small bugfix: run the skill to commit the fix as 'fix(scope): description' and submit a PR for review.
  • Complete a feature branch: create a structured commit and push a PR with the feature summary and linked issue.
  • Batch minor docs updates: commit docs changes with a conventional message and open a PR for review.
  • Prepare a quick patch during code pairing: commit paired changes and immediately request a review from the partner.

FAQ

Can I pass custom commit message arguments?

Yes. The skill accepts the same arguments used by the commit step, so you can supply a conventional message or allow prompts.

What happens if the commit step fails?

If the commit step fails, the skill stops and does not attempt to submit a PR. Fix the issue and rerun the skill.