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

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

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

This skill creates conventional commits, opens PRs, verifies approvals, and ensures deploy success across iterations for AI-assisted development.

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

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

Files (1)

SKILL.md

585 B

---
name: git-commit-submit-pr-deploy-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. As well as making sure the resutling deploy succeeds.
allowed-tools: ["Bash"]
---

Run the /git-commit-submit-pr-and-verify with $ARGUMENTS. Once the merge is complete, follow the resulting deploy and fix anything that breaks with the deploy and then follow this process again with a new PR until the deploy succeeds.

Overview

This skill helps you create conventional commits for your current changes, submit the current branch as a pull request for review, verify the PR approval, and ensure the resulting deployment succeeds. It encodes a repeatable loop: commit, submit PR, verify, merge, monitor deploy, and remediate failures until the deploy is stable. The workflow is optimized for TypeScript projects using code governance and automated enforcement.

How this skill works

You run the command to create a conventional commit for staged changes and push the branch. The skill opens a pull request with the current branch, waits for required reviews or checks, and verifies that the PR is approved. After merge, it monitors the deployment pipeline, reports failures, and guides corrective actions; once fixed, you repeat the flow with a new PR until deployment passes.

When to use it

Ready to package changes for code review and CI/CD deployment
You need to enforce conventional commit messages for traceability
When automated checks or branch protection require PR approval before merge
To validate that a merged change successfully deploys to target environments
When you want a repeatable loop to fix deploy-time regressions

Best practices

Write clear conventional commit messages (type(scope): summary) to surface intent
Run local tests and linters before creating the commit to reduce CI failures
Keep PRs small and focused to speed review and isolation of regressions
Monitor CI/CD logs immediately after merge and address failures in the same branch if safe
If a deploy fails, create targeted fixes and submit a follow-up PR rather than hotpatching main

Example use cases

Add a TypeScript utility and submit a PR that teams must review before merging
Fix a production bug that surfaces only after merging and deployment; iterate until stable
Enforce commit conventions across a repository using automated checks during PR creation
Validate that feature branches pass integration tests and deploy to staging successfully
Automate the developer flow when branch protection rules require approvals and green CI

FAQ

What defines a conventional commit for this skill?

Use the conventional commit format like feat(scope): short description or fix(scope): short description so CI and release tooling can parse intent.

What if the PR is approved but the deploy fails?

Investigate CI/CD logs, create a targeted fix in a new branch or the same branch if allowed, submit another PR, and repeat the verify-and-deploy loop until the deployment succeeds.