Best fit
A plausible ignore file can still miss a nested environment file, private key, credential export, or negation that re-includes sensitive material.
// Developer Tools
Gitignore Coverage Preflight
Check supplied repository paths and ignore patterns for uncovered or already tracked sensitive-looking files.
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
- Review a repo inventory before first push.
- Find sensitive-looking tracked paths.
- Inspect ignore negations before sharing a project.
What it returns
- findings.csv with stable codes and record identifiers
- review-manifest.csv with every reviewed item
- result.json with READY, REVIEW, or BLOCK gate
- report.md with a human-readable decision handoff
A representative input and result
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
- Read access to one user-supplied local JSON evidence file.
- Write access only to the selected local output directory.
- No browser, network, credential, account, environment-variable, or external-action permission.
Known limitations
- Filename heuristics cannot detect secrets inside innocently named files.
- The normalized manifest must reflect the repository state being reviewed.
- It does not alter Git history, untrack files, or edit ignore rules.
// choose with context
Is Gitignore Coverage Preflight the right skill?
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
- Normalized UTF-8 JSON input documented in the package. Python 3.10 or newer on Windows, macOS, or Linux. Local files only; no live account or provider connection.
- Version
- 1.0.0
- Licence
- Review the package licence and seller terms at the linked destination.
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