playbooks

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

git-commit-submit-pr-and-verify skill

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

This skill creates conventional commits, submits a pull request, and verifies approval, auto-merging after checks pass.

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

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

Files (1)
SKILL.md
537 B
---
name: git-commit-submit-pr-and-verify
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. And then verifying the pull request was approved.
allowed-tools: ["Bash"]
---

Run the /git-commit-and-submit-pr with $ARGUMENTS and set the PR to auto-merge. Fix any pre-commit or pre-push issues and then follow the pr, make sure all checks pass and comments are resolved or addressed. Fix anything that is broken and repeat.

Overview

This skill automates creating conventional commits for the current changes, submits the current branch as a pull request, and verifies the PR is approved and ready to merge. It sets the PR to auto-merge, runs through pre-commit and CI checks, and iterates on failures until all checks and review comments are resolved. The goal is a reproducible, policy-compliant PR flow that reduces manual steps and ensures quality gates are met.

How this skill works

You run the underlying git-commit-and-submit-pr command with any required arguments to produce a conventional commit and open a pull request with auto-merge enabled. The skill detects and fixes or reports pre-commit/pre-push issues, watches the PR build and status checks, and follows review activity. If checks fail or reviewers request changes, it prompts or applies fixes, updates the branch, and re-runs validation until the PR is approved and mergeable.

When to use it

  • You have local changes that should follow conventional commit standards and be submitted for code review.
  • You want the pull request opened with auto-merge enabled to reduce manual merge work after approval.
  • You need automated handling of pre-commit hooks, linters, or test failures before creating the PR.
  • You are enforcing review and CI gates and want the skill to monitor and verify approval and passing checks.
  • You prefer an iterative workflow where the skill applies fixes and re-validates until the PR is clean.

Best practices

  • Ensure working tree is clean and tests run locally before invoking the skill to minimize iterations.
  • Provide clear, conventional-commit style messages to improve changelog and review clarity.
  • Address lint and unit-test failures locally when possible; use the skill to catch CI-only issues.
  • Keep PRs focused and small so automated fixes and reviewer feedback are easier to manage.
  • Review any automated changes the skill applies before final approval to maintain code quality.

Example use cases

  • Add a bugfix branch, run the skill to create a conventional commit, submit a PR, and monitor until merge.
  • Implement a small feature, let the skill enforce commit style, and enable auto-merge after approvals.
  • Run the skill in a CI-assisted workflow to detect and fix pre-push hooks, then re-run checks automatically.
  • Use it when multiple reviewers are required: the skill watches approvals and ensures all checks pass before merging.

FAQ

What happens if pre-commit hooks fail?

The skill reports the failures and attempts automated fixes if available; otherwise it prompts you to resolve issues, update the branch, and re-run validation.

How does auto-merge behave if new issues appear after approval?

Auto-merge waits until all required checks are green and any required reviews remain satisfied. If new failures or review requests appear, the skill re-checks and pauses auto-merge until those are resolved.