Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    GitGov IA — Gobernanza y Auditoría Git

    1

    Standardize Git governance with automated auditing, secret detection, and AI authorship tracking.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    GitGov IA — Gobernanza y Auditoría Git

    GitGov IA — Gobernanza y Auditoría Git

    Example session with this skill installed

    Run a security audit on the last 5 commits and check my local git identity.

    • Read your context and instructions
    • Compiled the gitgov ia

    I have performed a security and authorship audit on the repository. I checked the last 5 commits for sensitive patterns and verified your local Git configuration against project standards.

    Git Audit & Security Report

    CategoryCheckStatusFindings / Evidence
    Identityuser.nameOKdev-user-01
    Identityuser.emailOKdev@company.local
    AuthAuthor vs CommitterOKNo discrepancies found in last 5 commits.
    SecuritySecret ScanningWARNINGPotential API key pattern in config/env.template (line 12).
    Security.gitignoreOKRules for .env and *.pem are present.
    CommitsConventional FormatFAILCommit a1b2c3d message "update" is too generic.
    AI TrailAI-Assisted TrailerMISSING2 commits show AI patterns but lack AI-Assisted: true.

    Findings Summary:

    Critical: A potential secret was detected in a template file. Although it is a template, ensure no real keys were used for testing.

    • Compliance: Commit messages are not following the type(scope): description format.
    • Governance: Identified 2 commits that appear to be generated by an agent but lack the required metadata trailers.

    Next steps

    1. Review config/env.template and redact any literal values found.
    2. Update your local commit template to include the AI-Assisted trailer if you are using an LLM.
    3. Use the git-commit-conventions skill to refactor the non-compliant commit messages before the next push.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    GitGov IA provides a standardized governance framework for Git repositories, focusing on auditability, security, and clear authorship. It solves the problem of inconsistent commit history, accidental credential leaks, and the lack of transparency in AI-assisted coding. Use this skill to enforce high-quality standards across your version control workflow without manual policing.

    What it does

    • Enforce Commit Standards ensures every message follows Conventional Commits with specific tags for AI assistance.
    • Audit Repository State generates reproducible reports on Git configuration, branch health, and commit quality.
    • Validate Authorship prevents impersonation or accidental identity leaks by verifying local user settings and commit signatures.
    • Detect Secrets scans staged changes and recent history for leaked tokens or credentials using non-destructive inspection.
    • Manage Branching Strategy defines and monitors integration flows, PR requirements, and protection rules.
    • Track AI Provenance registers a verifiable trail of which changes were generated by AI and which were human-reviewed.

    How it works

    1. Initialize Audit by running a scan of your local Git environment and recent commit metadata.
    2. Review Identity to ensure your local user.name and user.email match project requirements before committing.
    3. Analyze Changes with the security and convention tools to identify risks or non-compliant formatting.
    4. Generate Documentation for Pull Requests or Releases, including AI-assisted trailers and changelog summaries.

    Frameworks & tools

    This skill works with any project using the Git CLI. It follows industry standards like Conventional Commits and Semantic Versioning (SemVer) and is compatible with major platforms like GitHub, GitLab, and Bitbucket.

    Why this beats prompting it yourself

    Generic prompts often miss technical nuances like the difference between an author and a committer or the danger of rebase on shared branches. This skill implements a strict governance protocol that treats AI participation as a trackable data point rather than a guess, ensuring your audit trail is professional and legally defensible.

    Use cases

    • Auditing a repository before a major release to ensure compliance.
    • Standardizing commit messages across a team using AI coding tools.
    • Detecting accidental secret exposure in staged files before pushing.
    • Documenting AI involvement in codebase contributions for legal or internal policy.

    Known limitations

    This skill performs non-destructive inspections and will not rewrite history or rotate keys automatically. Security scans rely on heuristics and require human verification of potential findings.

    Requires Git CLI installed. Non-destructive only: will not automatically rewrite history or rotate secrets. Identifies patterns but requires human verification for final risk assessment.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed today

    Requires

    Python
    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Environment Variables
    Listedtoday

    What's inside

    Frequently Asked Questions

    GitGov IA is compatible with any environment using the Git CLI, including popular platforms like GitHub, GitLab, and Bitbucket. It can be integrated into your local workflow or used as a compliance layer for AI-assisted development pipelines.

    The skill scans staged changes and recent history for leaked tokens or credentials using non-destructive inspection. While it identifies risks, it does not automatically rewrite history or rotate keys, ensuring you maintain full control over any remediation steps.

    This skill adds a verifiable trail to your commit metadata, distinguishing between AI-generated code and human-reviewed changes. This creates a professional audit trail that is essential for legal compliance and internal policy regarding AI provenance.

    Setup is straightforward: start by initializing a local audit of your Git environment to scan metadata and configuration. The skill then guides you through identity verification and change analysis to ensure your workflow meets project-specific governance standards.

    You receive the full governance framework, including automated auditing scripts, commit standard enforcers, and security scanning tools. The purchase also includes updates to the governance protocols as Git standards and AI documentation requirements evolve.

    No, GitGov IA performs non-destructive inspections. It identifies non-compliant formatting or configuration risks but will not force rebase, rewrite history, or alter your repository state without your direct manual intervention.

    New in Code Quality & Review