commit

Coordinate commit, push, and PR steps with evidence for a branch.

1|Updated Apr 18, 2026

Search Tags:#git #commit #evidence #branch-management #pull-request #pr-description

Ready to run

npx skills add https://github.com/mopeyjellyfish/flywheel --skill commit-mopeyjellyfish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/mopeyjellyfish/flywheel/tree/main/skills/commit
Command: npx skills add https://github.com/mopeyjellyfish/flywheel --skill commit-mopeyjellyfish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Finish a branch cleanly by coordinating commit, push, and PR steps with evidence.

Core Features & Use Cases

Finish workflow: ensure changes are committed and pushed, and PRs are created or refreshed with a clear, policy-compliant description.
Evidence-driven PRs: include safe, designed evidence into PR body per guidelines.
Operational safety: gate checks and evidence integration to prevent unsafe merges.

Quick Start

Finish a branch by committing, pushing, and creating or refreshing the PR with evidence.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I finish a git branch cleanly and create a PR with evidence?▼

To finish a git branch cleanly, you coordinate commit, push, and pull request steps together. This ensures changes are committed, pushed, and packaged with a policy-compliant PR description containing safe evidence.

How do I generate a PR description that includes evidence for branch management?▼

Generating an evidence-driven PR description involves integrating safe, designed evidence into the PR body per guidelines. This ensures your branch management workflow satisfies operational governance and policy-managed gating requirements.

How can I prevent unsafe merges during a git pull request workflow?▼

Preventing unsafe merges during a git pull request workflow requires applying operational safety gate checks. These checks coordinate evidence integration to ensure your branch history is signed-off and PR-ready before merging.

What is the best way to automate git commit, push, and PR creation for feature branches?▼

The best way to automate git commit, push, and PR creation is using a structured finish flow. This coordinates the three actions across feature development or bug fix workflows, ensuring scalable collaboration and a signed-off history.

Do I need a signed-off history to refresh a pull request with new evidence?▼

Yes, a signed-off history is required to refresh a pull request properly. Applying evidence handling and PR templating ensures your branch maintenance tasks meet operational governance and policy-managed gating requirements.