commit-push

Group content-type changes into commits and push after security review.

Updated May 25, 2025
One-click install
npx skills add https://github.com/temple-slope/dotfiles --skill commit-push-temple-slope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push
Source: https://github.com/temple-slope/dotfiles/tree/main/dot_claude/skills/commit-push
Command: npx skills add https://github.com/temple-slope/dotfiles --skill commit-push-temple-slope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Group changes by content type, enforce a security review before committing, and push only after approval.

Core Features & Use Cases

  • Group related edits into coherent commits by category (docs, code, configs, secrets) to simplify review and history.
  • Enforce a pre-push security review to detect secrets, credentials, and risky changes before sharing.
  • Use case: large projects with mixed-file modifications where atomic, reviewable commits improve traceability and compliance.

Quick Start

Run the commit-push workflow after completing a security review to group changes, commit them by type, and push to the remote.

Frequently Asked Questions about commit-push

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

FAQPage Schema
How do I group git changes by type before committing and pushing?

It groups mixed-file modifications into coherent commits by content type, such as docs, code, and configs, simplifying review and traceability before pushing to remotes.

How do I enforce a security review before pushing commits to a remote?

Pre-push security review detects secrets, credentials, and risky changes before sharing. This workflow enforces the validation process, ensuring only approved and safe code modifications are pushed to remotes.

What is the best way to organize atomic commits in large projects?

Grouping related edits into category-specific commits guides commit granularity to improve history traceability and compliance for large projects.

Can I automate grouping code, docs, and configs into separate git commits?

Yes, the workflow runs after completing a security review to automatically organize changes by category and push them securely to remotes.

Why do I need a security review before sharing code changes to remotes?

A security review is needed to detect secrets, credentials, and risky modifications, preventing sensitive data exposure and enforcing safe pushing practices across development projects.