git-ops

Automate git workflows for story-based development in GitHub Next.js projects.

Updated Nov 8, 2022
One-click install
npx skills add https://github.com/gvinokur/qatar-prode --skill git-ops-gvinokur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-ops
Source: https://github.com/gvinokur/qatar-prode/tree/main/.claude/skills/git-ops
Command: npx skills add https://github.com/gvinokur/qatar-prode --skill git-ops-gvinokur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing story-based Git workflows manually is error-prone and noisy; this Skill consolidates plan commits, draft PR creation, CI/CD polling, merge procedures, and worktree cleanup into repeatable, auditable steps to reduce mistakes and context bloat.

Core Features & Use Cases

  • Plan commits & draft PRs: Commit implementation plans with co-author attribution, push feature branches, and open draft PRs linked to the issue.
  • CI/CD polling and validation: Wait for Vercel and SonarCloud checks, report results, and fetch Sonar issues before merge decisions.
  • Story completion & cleanup: Merge PRs according to project rules, close issues, delete branches, update project status, and synchronize the main worktree.
  • Use case: Use when a planned story has been reviewed and you need to commit the plan, create a DRAFT PR, iterate on the plan, validate CI checks, and complete the story with automated cleanup.

Quick Start

Use the git-ops skill to commit the plan, push the feature branch, and create a draft PR for the current story.

Frequently Asked Questions about git-ops

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

FAQPage Schema
How do I automate git workflows for story-based development?

Automate git workflows for story-based development by consolidating plan commits, draft PR creation, CI/CD polling, and merge procedures into repeatable, auditable steps to reduce manual errors.

How do I create a draft PR and link it to a GitHub issue?

Create a draft PR by pushing your feature branch, fetching the issue title, and opening a draft PR linked to the issue with co-author attribution for the committed implementation plan.

Can I automate Vercel and SonarCloud CI checks before merging a pull request?

You can automate CI checks by polling Vercel and SonarCloud, reporting validation results, and fetching Sonar issues to ensure checks pass before executing merge decisions.

Does this automation work with Next.js projects using git worktrees?

Yes, this automation applies to GitHub-based Next.js projects and supports feature worktrees, branch creation, PR lifecycle management, and worktree synchronization during story completion.

How do I clean up git branches and worktrees after a story is merged?

Clean up branches and worktrees by invoking project helper scripts to merge PRs, close issues, delete branches, update project status, and synchronize the main worktree after story completion.

What is the best way to manage PR lifecycle and story completion in GitHub?

Manage PR lifecycle by automating draft PR creation, polling CI/CD checks, and using helper scripts to merge, close issues, and clean worktrees, reducing manual workflow errors and context bloat.