git

Automates Git workflows with conventional commits, staged analysis, and secret scanning.

2|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/hotriluan/alkana-dashboard --skill git-hotriluan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/hotriluan/alkana-dashboard/tree/main/.opencode/skill/git
Command: npx skills add https://github.com/hotriluan/alkana-dashboard --skill git-hotriluan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Git operations with conventional commits can be error-prone without a disciplined workflow. This skill enforces conventional commits, staged analysis, and safety checks to streamline collaboration and reduce mistakes.

Core Features & Use Cases

  • Staging, committing, pushing, PR creation, and merges using conventional commits.
  • Auto-splits commits by type/scope to maintain a clean, readable history.
  • Security scans for secrets during the commit workflow to prevent leaks.
  • Activation of the context-engineering skill to enhance reliability.

Quick Start

Run the git-manager subagent to perform staged commits, pushes, PRs, and merges with conventional-commit rules and secret scanning.

Frequently Asked Questions about git

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

FAQPage Schema
How do I automate conventional commits in my Git workflow?

Automate conventional commits by running the git-manager subagent to handle staging, committing, pushing, and PR creation. It analyzes staged changes and auto-splits commits by type and scope to maintain a clean, readable project history.

How does secret scanning work during the Git commit workflow?

Secret scanning runs automatically during the staging and committing process to detect and prevent sensitive data leaks. It inspects staged changes before finalizing the commit, ensuring security checks are enforced deterministically throughout the workflow.

Can I automate pull request creation and merges using safe Git workflows?

Yes, you can automate pull request creation and merges safely. The workflow enforces deterministic behavior and compliance rules during these operations, streamlining collaboration while reducing the risk of manual errors or unauthorized merges.

Do I need any special dependencies to enforce conventional commit workflows?

No special dependencies are required beyond a standard Git environment. The workflow operates independently with deterministic behavior and can optionally be extended via references to enforce stricter compliance rules.

Why should I split commits by type and scope in version control?

Splitting commits by type and scope enforces conventional commit standards, which keeps your project history clean and readable. This structured approach streamlines team collaboration and reduces mistakes during automated staging and pushing.

What is the best way to prevent errors when pushing conventional commits?

The best way to prevent errors is to use an automated workflow with built-in safety checks. It enforces conventional commit rules, performs secret scans, and activates context-engineering to enhance reliability before code is pushed.