commit-push

Automate secure Git commits and GitHub pull requests with Conventional Commits.

Updated Apr 29, 2024
One-click install
npx skills add https://github.com/takaokanbe/dotfiles --skill commit-push-takaokanbe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push
Source: https://github.com/takaokanbe/dotfiles/tree/main/config/claude/skills/commit-push
Command: npx skills add https://github.com/takaokanbe/dotfiles --skill commit-push-takaokanbe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually committing code changes and creating pull requests on GitHub often leads to critical errors such as accidentally committing sensitive files like credentials, violating team commit message conventions, or creating duplicate pull requests for the same branch, which creates security risks and wastes team time.

Core Features & Use Cases

  • Sensitive File Protection: Automatically detects and excludes confidential files (e.g., .env, private keys) from staging to prevent accidental exposure of credentials.
  • Conventional Commits Enforcement: Validates commit messages against standard type and formatting rules to maintain a clean, readable project history.
  • Intelligent PR Management: Automatically detects existing open pull requests for the current branch to avoid duplicates, and handles new PR creation or existing PR updates as needed.
  • Use Case: For a developer who just finished fixing a bug in a feature branch, this skill automates the entire process of staging the changed files, creating a standards-compliant commit, pushing the branch, and creating a pull request for review, all while ensuring no sensitive data is leaked.

Quick Start

Use the commit-push skill to commit your recent code changes and create a pull request for the current feature branch.

Frequently Asked Questions about commit-push

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

FAQPage Schema
How do I prevent accidentally committing sensitive files like .env or private keys in Git?

To prevent committing sensitive files, automated Git workflows can detect and exclude confidential files like credentials from the staging area. This ensures private keys and environment files are blocked before a commit is created.

How do I enforce Conventional Commits standards for my GitHub pull requests?

Enforcing Conventional Commits standards involves validating commit messages against standard type and formatting rules before pushing. This maintains a clean, readable project history for GitHub-hosted repositories by rejecting non-compliant messages.

What is the best way to avoid creating duplicate pull requests for the same Git branch?

The best way to avoid duplicate pull requests is through intelligent PR management that automatically detects existing open pull requests for the current branch. It handles new PR creation or updates existing PRs to prevent duplicates.

Can I automate staging individual files and pushing them to GitHub?

Yes, you can automate staging individual files and pushing to GitHub by applying individual file staging rules within the workflow. This automatically stages changed files, creates a compliant commit, and pushes the branch.

Does this automated commit and PR workflow work without any external dependencies?

Yes, the automated commit and PR workflow operates without external dependencies. It standardizes commit messages, enforces sensitive file exclusion, and prevents duplicate PRs natively for GitHub-hosted repositories.