← Back to Skills Marketplace
wimi321

Git Commit PR Workflow

by wimi321 · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
82
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install git-commit-pr-workflow
Description
Use when the user wants the full git workflow: branch creation if needed, commit, push, and PR create or update with a concise summary and test plan.
README (SKILL.md)

Git Commit PR Workflow

Use this skill for end-to-end git delivery from working tree to pull request.

Workflow

  1. Inspect branch state, diff against default branch, and existing PR state.
  2. Create a feature branch if still on the default branch.
  3. Stage and commit the relevant changes.
  4. Push the branch.
  5. Create or update the PR with a short title, summary bullets, and test plan.

Guardrails

  • No destructive git commands unless explicitly requested.
  • No force push to default branches.
  • Keep PR titles short and bodies structured.
  • Avoid committing secrets or unrelated changes.

Example Requests

  • Commit this work, push it, and open a PR.
  • Take the current changes to a polished PR with a test plan.

Inputs

  • Current git state
  • Default branch
  • Optional user instructions

Outputs

  • New commit
  • Pushed branch
  • Created or updated PR

Success Criteria

  • The right files were committed.
  • The branch was pushed safely.
  • The PR body accurately reflects the diff.

Non-Goals

  • Force-push workflows by default
  • Interactive git rebases

Source Provenance

Derived from src/commands/commit-push-pr.ts.

Usage Guidance
This skill appears to implement a normal git commit/push/PR workflow, but it omits key operational details. Before installing or using it: 1) Confirm which git hosting provider (GitHub/GitLab/Bitbucket) it will interact with. 2) Ask whether it requires the git CLI, the provider's CLI (e.g., gh), or specific environment credentials (GITHUB_TOKEN, GITLAB_TOKEN, or access to SSH keys). 3) Require explicit confirmation prompts before staging, committing, pushing, or creating PRs (especially pushes to remotes). 4) Run it in a safe/forked repository first and verify its behavior. 5) If you need stricter controls, request the skill declare required binaries and credentials or restrict it from performing remote PR creation automatically.
Capability Analysis
Type: OpenClaw Skill Name: git-commit-pr-workflow Version: 1.0.0 The skill bundle defines a standard Git workflow automation for branching, committing, pushing, and creating pull requests. It includes explicit guardrails in SKILL.md to prevent destructive commands, force-pushing to default branches, and the accidental commitment of secrets, with no evidence of malicious intent, data exfiltration, or prompt injection.
Capability Assessment
Purpose & Capability
The name/description align with committing, pushing, and opening/updating PRs. However, creating/updating PRs normally requires a git client plus remote-host authentication (e.g., gh/Hub API tokens or ssh keys). The skill declares no required binaries or credentials, which is unexpected for the stated purpose.
Instruction Scope
Runtime instructions tell the agent to inspect branch state, diffs, and existing PR state and then create or update PRs. Those operations imply reading repository state and interacting with an external git hosting service, but the skill doesn't specify which host or how to authenticate. The guardrails are reasonable but high-level; the skill grants the agent open discretion to determine 'relevant changes' to stage/commit.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest installation risk. There is nothing being downloaded or written to disk by the skill bundle itself.
Credentials
The skill requests no environment variables or config paths, yet performing remote PR operations normally requires credentials (API tokens or SSH keys) or a CLI (gh) that uses stored credentials. The omission is disproportionate/ambiguous: either the skill assumes existing host-level credentials (not declared) or it lacks a mechanism to create PRs as claimed.
Persistence & Privilege
always is false and the skill is user-invocable with normal autonomous invocation allowed. It does not request persistent installation or elevated platform privileges.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install git-commit-pr-workflow
  3. After installation, invoke the skill by name or use /git-commit-pr-workflow
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial extraction from local Claude Code source
Metadata
Slug git-commit-pr-workflow
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Git Commit PR Workflow?

Use when the user wants the full git workflow: branch creation if needed, commit, push, and PR create or update with a concise summary and test plan. It is an AI Agent Skill for Claude Code / OpenClaw, with 82 downloads so far.

How do I install Git Commit PR Workflow?

Run "/install git-commit-pr-workflow" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Git Commit PR Workflow free?

Yes, Git Commit PR Workflow is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Git Commit PR Workflow support?

Git Commit PR Workflow is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Git Commit PR Workflow?

It is built and maintained by wimi321 (@wimi321); the current version is v1.0.0.

💬 Comments