git

Automate Git staging, conventional commits, and GitHub CLI pull requests.

1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/locnbk2002/my-copilot --skill git-locnbk2002
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/locnbk2002/my-copilot/tree/main/my-copilot/skills/git
Command: npx skills add https://github.com/locnbk2002/my-copilot --skill git-locnbk2002

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates and standardizes Git operations, ensuring consistent commit messages, security checks, and efficient pull request creation.

Core Features & Use Cases

  • Conventional Commits: Automatically generates commit messages following the Conventional Commits specification.
  • Security Scanning: Scans staged changes for secrets, API keys, and sensitive information before committing.
  • Atomic Commits: Supports splitting changes into smaller, focused commits based on phases or directory structure.
  • Pull Request Creation: Facilitates the creation of pull requests with auto-generated titles and bodies.

Quick Start

Use the git skill to stage all changes, commit them with a conventional message, and push to the remote repository.

Frequently Asked Questions about git

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

FAQPage Schema
How do I automate git commits with conventional commit messages?

Automating git commits with conventional messages is achieved by staging changes and generating commit text that strictly follows the Conventional Commits specification. This ensures standardized commit history across your project without manual formatting.

Can I scan staged changes for secrets and API keys before pushing code?

Yes, you can scan staged changes for secrets and API keys before pushing code. The security scanning feature automatically detects sensitive information in staged files, preventing accidental exposure of credentials in your remote repository.

What is the best way to split changes into atomic commits based on directory structure?

Splitting changes into atomic commits based on directory structure involves dividing your staged files into smaller, focused commits grouped by project phases or folders. This maintains a clean, logical git history for targeted code reviews.

How do I create a pull request using the GitHub CLI with auto-generated titles?

Creating a pull request using the GitHub CLI with auto-generated titles requires pushing your committed code changes to the remote repository first. The tool then facilitates pull request creation by automatically generating the title and body content.

Does this git automation tool work without additional dependencies?

Yes, this git automation tool works without additional dependencies. It requires no external packages to stage, commit, and push code changes, though the GitHub CLI is utilized specifically for the pull request creation feature.