JustHandled Labs
Menu
// Developer Tools

Gitignore Coverage Preflight

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

We earn a commission on eligible purchases after a new Agensi signup through these links. We also sell our own skills on Agensi.

Format: Agent skill, not a browser app. You need an AI agent that can load its instructions and use the required tools.

Package requirements: Python 3.10+, a file-capable agent, normalized UTF-8 JSON input and a fresh output folder. The check itself needs no network access.

You get: findings.csv with stable codes and record identifiers, plus review-manifest.csv with every reviewed item.

Licence and purchase details

Review the package licence at the destination.

Review the offer and access method at your chosen marketplace. Agensi provides connected-agent access, not a download. Buying a skill does not include an AI-agent subscription or setup service.

Agensi access: Supporting-file delivery and seven synthetic execution controls passed in the creator-connected agent session. Load the delivered script in that session; do not assume a local scripts/ folder exists. Independent buyer unlock was not tested.

See tested hosts, versions and workflow limits.

What problem does Gitignore Coverage Preflight solve?

A plausible ignore file can still miss a nested environment file, private key, credential export, or negation that re-includes sensitive material.

Use it to

What it returns

A representative input and result

fixture-backed sample
input {"paths":["src/app.js",".env"],"patterns":[".env"],"tracked_paths":[]}
result READY; .env is covered by the supplied pattern and no sensitive tracked path is present.

Access and approval boundaries

Known limitations

What was checked in v1.0.1

Creator-connected Agensi delivery checked October 23, 2026: all four texts match the sealed package after CRLF-to-LF normalization; seven synthetic execution controls passed. Raw byte hashes differ by line endings. Independent buyer unlock was not tested.

The update corrects nested and root-anchored matching, includes tracked paths omitted from the main inventory, rejects malformed inputs and preserves existing output files. These bounded tests are not a security certification.

// choose with context

Is Gitignore Coverage Preflight the right skill?

Best fit

A plausible ignore file can still miss a nested environment file, private key, credential export, or negation that re-includes sensitive material.

It returns

findings.csv with stable codes and record identifiers. review-manifest.csv with every reviewed item.

Do not use it as

Filename heuristics cannot detect secrets inside innocently named files.

Compatibility, access, version, and licence

Reads or accesses
Declared local scope: one owner-selected local JSON input, one owner-selected local output directory.
Compatibility
Python 3.10+ and a file-capable agent. Supply UTF-8 JSON and a fresh output directory. Agensi delivers the supporting script for in-session execution; do not assume a local scripts/ folder exists. No network access is needed for the check.
Version
Package v1.0.1; Agensi platform release v1.1. Verified October 23, 2026.
Licence
Review the package licence and seller terms at the linked destination.

What happens next

Open the Agensi listing, check the current offer and connect a supported agent. Agensi loads the skill through its connector; it no longer provides a download. Approve any purchase before use. Check Agensi’s current connection guide before changing an existing connection.

Questions

Does it change or upload anything?

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

Is this an AI judgment?

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

What does a ready result mean?

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

How does malformed input behave?

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

Can I audit the result?

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

Gitignore Coverage Preflight keeps proof and approval boundaries visible.

The listing includes the tested package, realistic samples, declared permissions, and known limitations.

Get Gitignore Coverage Preflight on Agensi