Verified:GitHub

git

Manage git branches, commits, and PR/MR workflows across GitHub, GitLab, and Forgejo.

2|Updated Apr 6, 2026

Search Tags:#automation #git #devops #version control #security #compliance

One-click install

npx skills add https://github.com/iuliandita/skills --skill git-iuliandita

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: git
Source: https://github.com/iuliandita/skills/tree/main/skills/git
Command: npx skills add https://github.com/iuliandita/skills --skill git-iuliandita

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, glab, fj, gitleaks, cosign, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill resolves the fragmentation and inconsistency in managing git operations across multiple forges like GitHub, GitLab, and Forgejo, ensuring audit-grade history and compliance.

Core Features & Use Cases

Multi-Forge Operations: Seamlessly handle commits, branches, and PR/MR workflows across different platforms using native CLI tools.
Compliance & Security: Enforce PCI-DSS 4.0 standards through automated commit signing, secret scanning, and branch protection controls.
Use Case: When working in a team that mirrors code between GitHub and a self-hosted Forgejo instance, use this Skill to synchronize branches, cut releases, and maintain a clean, signed audit trail without manual errors.

Quick Start

Use the git skill to create a new feature branch named feat/auth-update and push it to the origin remote.

Frequently Asked Questions about git

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

FAQPage Schema

How do I manage git branches and PR workflows across GitHub, GitLab, and Forgejo simultaneously?▼

Multi-forge git workflows are managed by integrating native CLI tools like gh, glab, and fj to provide a unified interface for branch synchronization and pull request lifecycle management.

How do I automate secret scanning and commit signing for PCI-DSS compliance in git?▼

Automated secret scanning and commit signing for PCI-DSS compliance in git are enforced by running gitleaks for detection and cosign for cryptographic signing to generate audit trails.

What is the best way to synchronize code mirrors between GitHub and a self-hosted Forgejo instance?▼

Synchronizing code mirrors between GitHub and Forgejo involves using the unified CLI interface to cut releases, synchronize feature branches, and maintain a clean audit history without manual errors.

Does this git workflow tool require specific CLI clients to run multi-forge operations?▼

Multi-forge operations require specific CLI clients installed as dependencies, including gh for GitHub, glab for GitLab, and fj for Forgejo, alongside git, gitleaks, and cosign.

Can I enforce branch protection controls and generate audit trails for enterprise version control?▼

Branch protection controls and audit trails for enterprise version control are enforced through automated compliance checks that maintain commit history integrity and generate signed records.

Why does multi-forge repository lifecycle management require automated commit signing?▼

Multi-forge repository lifecycle management requires automated commit signing to ensure audit-grade history, verify commit authenticity across different platforms, and meet PCI-DSS 4.0 security standards.