More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    🛡️ Gitignore Coverage Preflight

    1

    Check supplied repository paths and ignore patterns for uncovered or already tracked sensitive-looking files.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    🛡️ Gitignore Coverage Preflight

    🛡️ Gitignore Coverage Preflight

    Example session with this skill installed

    Check this synthetic inventory using the included helper, writing reports to a new output folder. Explain the gate before suggesting any change.

    {"paths":[".env","app/.env","services/api/.env","README.md"],"patterns":["/.env"],"tracked_paths":[]}

    • Read your context and instructions
    • Compiled the gitignore coverage preflight
    • Generated the data export

    Synthetic execution example

    The helper returned BLOCK. The root-anchored /.env pattern covers the root .env file, but not the two nested environment files. This is a filename-based finding, not evidence that those files contain secrets.

    PathCoverageTracking
    .envignoreduntracked
    app/.envvisibleuntracked
    services/api/.envvisibleuntracked
    README.mdvisibleuntracked

    Machine-readable result

    {"profile":"gitignore-coverage-preflight","gate":"BLOCK","recordsReviewed":4,"findingCount":2,"counts":{"block":2}}
    

    Findings

    • SENSITIVE_PATH_UNCOVERED: app/.env
    • SENSITIVE_PATH_UNCOVERED: services/api/.env

    Files produced

    findings.csv, review-manifest.csv, result.json and report.md.

    Next step

    Review whether the nested files should be ignored, confirm the intended rules with Git, and rerun with an updated inventory in a new output folder. No repository files or ignore rules were changed by this run.

    findings.csv

    CSV · data export

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    About this skill

    Gitignore Coverage Preflight checks a supplied JSON inventory of repository paths, tracked paths and one root-level ignore-pattern list. It flags sensitive-looking filenames that remain uncovered or are already tracked, then writes findings.csv, review-manifest.csv, result.json and report.md into a fresh output directory.

    Package v1.0.1 corrects root-anchored and nested matching, includes tracked paths omitted from the main inventory, rejects duplicate JSON keys and malformed paths, and preserves existing output directories.

    This is a case-sensitive, supplied-evidence preflight—not a repository crawler, secret-content scanner or complete Git ignore implementation. Review its gate and findings before deciding what to change. It does not edit ignore rules, untrack files, rewrite Git history or certify that a repository is safe.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.

    Filename heuristics do not detect secrets inside innocently named files. Supply a complete, current path inventory, tracked-path list and root-level ignore-pattern list. Matching is case-sensitive. Nested/global ignore files and unsupported pattern syntax require review with Git; this is not full Git parity. A READY gate covers only the supplied evidence. Exit code 0 means the run completed, not that the gate passed. Existing output directories are refused. No rules, tracked files or history are changed.

    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 buying a skill.

    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 25 days ago

    Software
    Python

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    File Scopes

    one
    owner-selected
    local
    JSON
    input
    output
    directory

    The checker is deterministic and self-contained.

    Listed3 months ago
    Updated25 days ago

    What's inside

    Frequently Asked Questions

    No. It reads supplied local evidence and writes only to the selected output directory.

    No. The packaged checker is deterministic and applies documented rules to the supplied input.

    It means no automated finding was produced. The responsible owner still reviews the original source and decides what to do.

    Invalid JSON, duplicate identifiers, missing required arrays, and invalid core values fail closed.

    Yes. Every finding carries a stable code, record identifier, severity, source, and message.