commit-and-push

Automate feature-branch commits, pushes, and PR creation for the Irreden Engine.

8|Updated Oct 11, 2023
One-click install
npx skills add https://github.com/jakildev/IrredenEngine --skill commit-and-push-jakildev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-and-push
Source: https://github.com/jakildev/IrredenEngine/tree/main/.claude/skills/commit-and-push
Command: npx skills add https://github.com/jakildev/IrredenEngine --skill commit-and-push-jakildev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates end-to-end packaging of work into a reviewable PR on the Irreden Engine repository, enabling a repeatable, branched workflow instead of direct master commits.

Core Features & Use Cases

  • End-to-end PR flow: create a short-lived feature branch from master, commit changes, push, and open a PR for reviewer inspection.
  • Guardrails and workflow modes: includes pre-commit checks, stack-aware PR chaining, and automated PR body generation to keep changes organized.
  • Use case: when preparing a slice of work for review, enabling team members to track progress via PRs and maintain master safety.

Quick Start

Initiate the feature-branch PR flow by committing changes, pushing the branch, and opening the PR for review.

Frequently Asked Questions about commit-and-push

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

FAQPage Schema
How do I automate git commit, push, and pull request workflows?

Automating git commit, push, and pull request workflows involves orchestrating end-to-end PR flows from feature-branch commits to PR creation. This Skill enforces safety checks like branch isolation and GitHub authentication to ensure proper review governance.

What is stack-aware PR chaining and how does it work?

Stack-aware PR chaining connects dependent pull requests in parallel-agent workflows with per-branch worktrees. It ensures proper review governance by linking stacked changes, guiding when to commit, push, or open PRs while protecting the master branch.

How do I create a feature branch and open a PR for code review?

Creating a feature branch and opening a PR for code review requires initiating the feature-branch PR flow. This process commits changes, pushes the isolated branch, generates an automated PR body, and opens the PR for reviewer inspection.

Can I use parallel-agent workflows with per-branch git worktrees?

Yes, parallel-agent workflows with per-branch git worktrees are fully supported. The Skill applies master-protective PRs and branch isolation to ensure parallel changes remain organized and safely separated before merging.

What are the limitations of automated PR generation for master-protective review?

Automated PR generation for master-protective review requires GitHub authentication and strict branch isolation. It is designed specifically for the Irreden Engine repository and may not apply to direct master commit workflows outside its guarded ecosystem.