Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    .gitignore

    1

    Audit and adopt standardized gitignore rules to separate private working records from public documentation.

    $3

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    .gitignore

    .gitignore

    Example session with this skill installed

    Audit the current project for ignore rule gaps and separate my private dev notes in docs/ from the public API specs.

    • Read your context and instructions
    • Compiled the gitignore

    I have audited the repository's ignore configuration and identified several issues where private working notes are currently exposed or improperly classified.

    Audit Report: Git Visibility & Documentation

    Finding TypePath/PatternStatusRecommendation
    Tracked Privatedocs/internal/roadmap_2024.mdEXPOSEDMove to ignored private path and untrack.
    Broad Ignoredocs/OVER-INCLUSIVELift ignore; specifically ignore .private/ and .notes/.
    Missing Pattern*.log, .env.localRISKAdd to .gitignore to prevent accidental commits.
    Visibility Conflictdist/TRACKEDFiles in dist/ are currently tracked despite ignore rule.

    Proposed Changes

    1. Merge Asset: Add standard environment and OS-level ignore patterns from the reusable asset.
    2. Refactor Docs: Move private files from docs/ to docs/.private/ while keeping docs/api-spec.md public.
    3. Index Cleanup: Generate the commands to remove already tracked private files from the Git index.

    Next steps

    • Run gitignore apply to merge the standardized patterns and relocate private notes.
    • Review the docs/ structure to ensure public links to API specs remain functional.
    • Execute git rm --cached on the identified tracked-private files to respect new ignore rules.

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

    About this skill

    Loose .gitignore rules lead to leaked secrets, bloated repositories, and private working notes accidentally becoming public. This skill audits your existing ignore patterns and implements a structured strategy to separate private records from public product documentation.

    What it does

    • Standardize patterns by merging a reusable, battle-tested gitignore asset into your project.
    • Isolate documentation by lifting broad doc ignores and classifying records into public and private destinations.
    • Validate visibility using a Node-based verifier to ensure private paths are actually untracked.
    • Detect tracked secrets by identifying private material that was committed before the ignore rule existed.
    • Preserve custom rules by merging project-specific exclusions instead of blindly overwriting your configuration.

    How it works

    1. Inspection of existing ignore files, Git status, and project structure to classify files.
    2. Audit mode to report visibility findings and tracked-private issues without modifying files.
    3. Adoption workflow to merge the template, move private records, and update .gitignore.
    4. Verification via check-ignore.mjs to confirm the visibility contract is met post-change.

    Frameworks & tools

    This skill requires Git in the target project. The read-only verifier script requires Node 22+ for execution.

    Why this beats prompting it yourself

    Generic prompts often result in a generic .gitignore that deletes your specific build rules or fails to handle files already in the Git index. This skill follows a specific adoption guide that treats documentation as a first-class citizen, ensuring your internal notes stay out of the public repo while maintaining valid links.

    Use cases

    • Clean up a messy root directory by moving internal notes to ignored paths.
    • Audit a repository to find files that should be ignored but are currently tracked.
    • Implement a standardized gitignore across a multi-repo organization.
    • Safely extract public API contracts from internal-only documentation folders.

    Known limitations

    This skill is not for secret scanning, repository history cleanup, or full documentation content audits. It requires a local Git installation to function.

    Requires Git. Node 22+ needed for verification scripts. Does not perform history rewriting (git filter-repo) or deep secret scanning.

    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 1 month ago

    Permissions

    Write Files
    Read Files
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill audits your repository to identify leaked secrets and private notes that are currently tracked, then merges a battle-tested template with your custom rules to create a secure, organized file structure.

    The skill includes a pre-configured .gitignore template, an adoption workflow for moving private records, and a Node.js-based verification script to validate your visibility settings.

    Yes, the skill is designed to merge your existing project-specific exclusions with its standardized patterns rather than overwriting your configuration, ensuring your custom build rules remain intact.

    The core auditing and adoption functions work with any Git-enabled project, while the included visibility verifier requires a Node.js 22+ environment to execute its checks.

    While it identifies currently tracked files that should be ignored, it does not perform deep history scrubbing (like BFG or filter-branch); you will still need to purge those files from your Git history manually if they contain sensitive data.

    New in LLM Ops