Search skills.../

Commit Helper | Skills Pool

Skill File

Commit Helper

Create and execute git commit plans from YAML files - use when organizing changes into logical commits or when user wants help structuring their git history

mandersogit0 starsDec 21, 2025

Occupation
Categories: Automation Tools

Skill Content

Commit Helper Skill

⚠️ CRITICAL: NO AUTONOMOUS COMMITS ⚠️

NEVER execute commits without explicit user authorization.

This skill is for:

Creating commit plans - Always allowed
Previewing plans - Always allowed (read-only)
Executing commits - ONLY when user explicitly says to commit

If in doubt, ask the user before any git-modifying operation.

When to Use This Skill

Use this skill when the user needs to:

Organize changes into logical, well-structured commits
Create a commit plan for review before executing
Document what changes belong together
Manage complex multi-commit workflows

The Commit Plan Approach

Related Skills

Quick Install

Commit Helper

npx skills add mandersogit/brynhild-harness

Download Skill Open repository

Author: mandersogit
stars: 0
Updated: Dec 21, 2025
Occupation

On this page

01Commit Helper Skill

Instead of committing changes ad-hoc, create a YAML plan that:

Groups related changes into logical commits
Provides clear commit messages
Can be reviewed before execution
Can be re-run if interrupted (idempotent)

Commit Plan Format

Plans are YAML files. Naming convention: YYYY-MM-DD-description.yaml

Minimal Plan (Single Repo)

# Commit plan: Feature X
# Date: 2024-12-01

02

⚠️ CRITICAL: NO AUTONOMOUS COMMITS ⚠️

03When to Use This Skill

04The Commit Plan Approach

05Commit Plan Format

06Minimal Plan (Single Repo)

Software Developers

Gh Issues

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]

Automation Tools

Coding Agent (bash-first)

Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.

Security Triage

Triage GitHub security advisories for OpenClaw with high-confidence close/keep decisions, exact tag and commit verification, trust-model checks, optional hardening notes, and a final reply ready to post and copy to clipboard.

Openclaw Ghsa Maintainer

Maintainer workflow for OpenClaw GitHub Security Advisories (GHSA). Use when Codex needs to inspect, patch, validate, or publish a repo advisory, verify private-fork state, prepare advisory Markdown or JSON payloads safely, handle GHSA API-specific publish constraints, or confirm advisory publish success.

Github

GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.

Automation Tools

Fix

Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.

Software Developers