tkm:git

Automate git staging, committing, pushing, and pull requests with conventional commits.

Updated May 13, 2026
One-click install
npx skills add https://github.com/khapn-2933/agentic-coding-hands-on --skill tkm-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tkm:git
Source: https://github.com/khapn-2933/agentic-coding-hands-on/tree/main/.claude/skills/git
Command: npx skills add https://github.com/khapn-2933/agentic-coding-hands-on --skill tkm-git

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines git operations with conventional commit discipline, ensuring a clean and maintainable code history.

Core Features & Use Cases

  • Commit Management: Stage, commit, push, and open pull requests with conventional commit messages.
  • Auto-Splitting: Automatically splits commits by type and scope.
  • Secret Scanning: Scans for secrets before every commit to prevent data leaks.
  • Git Workflows: Provides a comprehensive set of git workflows for staging, committing, pushing, creating pull requests, and merging branches.

Quick Start

Use the tkm:git skill to stage and commit your changes with a conventional commit message.

Frequently Asked Questions about tkm:git

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

FAQPage Schema
How do I automate git operations with conventional commit discipline?

You can automate git operations with conventional commit discipline by using a tool that stages, commits, pushes, and opens pull requests while enforcing strict commit message formatting. This ensures a clean and maintainable code history.

Can I automatically split commits by type and scope in git?

Yes, you can automatically split commits by type and scope in git. The automation intelligently categorizes your staged changes, generating distinct conventional commit messages for different logical groupings within your code history.

How does secret scanning work before a git commit?

Secret scanning before a git commit works by automatically analyzing staged changes for sensitive data patterns prior to finalizing the operation. This prevents accidental data leaks by blocking the commit if secrets are detected.

Do I need any specific dependencies to use conventional commit workflows?

You need git and its associated tools installed in your environment to use these conventional commit workflows. The automation relies on these native git operations to execute staging, committing, pushing, and pull request creation.

What is the best way to manage pull requests with conventional commit messages?

The best way to manage pull requests with conventional commit messages is to use an automated workflow that handles branch merging and PR creation directly. This enforces a standardized code history across your repository.