More screenshots
Works with the AI Agents you already use
Gitignore Coverage Check
Check that .env files, private keys, key stores, tokens and Terraform state stay out of git, Docker images and npm packages, and that node_modules, build output, logs and editor junk are ignored.
$5
Gitignore Coverage Check
Example session with this skill installed
Check this project with gitignore-coverage-check.
- Read your context and instructions
- Compiled the gitignore coverage check
$ python3 scripts/check_gitignore.py examples/risky
BLOCK .env.production:4 G01 SECRET_FILE_NOT_GITIGNORED
STRIPE_SECRET_KEY=<redacted, 29 chars> (env file with secrets): re-included by !.env.production at .gitignore:4
Why: A file that holds secrets (an .env file with keys or passwords, a private key, a .p12/.pfx/.jks key store, service-account or OAuth credentials JSON, an .npmrc, .pypirc, .netrc or .git-credentials with a token or password, Terraform state, a Rails master key) is in the project and no ignore rule covers it, or git already tracks it. The next git add . commits it, and once pushed every clone and fork keeps it in history.
Safer: Add a pattern for it to .gitignore (.env*, !.env.example, *.pem, *.p12, .tfstate). If git already tracks it, run git rm --cached <file> and commit. Treat a secret that was ever committed or pushed as leaked and rotate it.
BLOCK .npmrc:2 G01 SECRET_FILE_NOT_GITIGNORED
BLOCK Dockerfile:5 G02 SECRET_COPIED_INTO_IMAGE
BLOCK package.json:2 G03 SECRET_IN_NPM_PACKAGE
REVIEW .dockerignore:2 G13 DOCKERIGNORE_PATTERN_ROOT_ONLY
REVIEW .gitignore:4 G14 NEGATION_REINCLUDES_SECRETS
REVIEW Dockerfile:5 G12 DOCKER_CONTEXT_NOT_FILTERED
REVIEW coverage/ G11 BUILD_OR_DEPENDENCY_FOLDER_NOT_IGNORED
REVIEW logs/server.log G15 LARGE_OR_DATA_FILE_NOT_IGNORED
REVIEW package.json:2 G16 NPM_PUBLISHES_LOCAL_FILES
REVIEW src/server.js.orig G17 OS_OR_EDITOR_FILE_NOT_IGNORED
REVIEW test/fixtures/client.p12 G18 TEST_SECRET_FILE_NOT_GITIGNORED
REVIEW worker/Dockerfile:3 G12 DOCKER_CONTEXT_NOT_FILTERED
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 15 files, 9 with ignore-rule or secret-file content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
You add a .npmignore with one line, test/, and npm stops reading your .gitignore, so the next npm publish ships .env.production. Your .dockerignore says *.log, but Docker matches that only at the root, so logs/ still goes into the image. This skill finds those and the other ways ignore rules quietly fail, and tells you how to fix each one.
Your agent runs a scanner on the project folder. It decides what each tool would really do: git (every .gitignore including nested and parent ones, .git/info/exclude, negation, anchoring, folder-only patterns, and the .git/index list of files git already tracks, which .gitignore never untracks), Docker (the .dockerignore at the build context root or the Dockerfile-specific one, root-only patterns, ** and ! re-includes, matched against every COPY and ADD), and npm (the "files" list, .npmignore replacing .gitignore, workspaces, always-included and never-included files). Secret files are recognized by their content, not only their name: an .env file is reported only when it holds a real secret value. It never runs git, docker or npm. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- G01: secret files git would commit or already tracks (.env with keys, private keys, .p12/.jks key stores, service-account JSON, .npmrc/.pypirc/.netrc tokens, Terraform state, Rails master.key)
- G02: secret files or the .git folder copied into a Docker image by COPY or ADD
- G03: secret files npm publish would include
REVIEW
- G11: node_modules, virtualenvs, caches and build output not ignored
- G12: COPY . with no .dockerignore, or dependency folders copied from the host
- G13: .dockerignore patterns that match only at the build context root
- G14: ! lines that re-include secret file names
- G15: files over 50 MB, SQLite databases, database dumps and logs not ignored
- G16: logs, coverage output and old tarballs npm publish would include
- G17: .DS_Store, Thumbs.db, swap files, *.orig and IDE workspace files not ignored
- G18: secret files in test, fixture and examples folders (often throwaway test keys, so check them)
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason and safer approach for each rule
- A risky and a safe example project, and the real report the scanner produces on the risky one
Limits It reads the files on disk. Your global git excludes file, build contexts set only in docker-compose or CI commands, and files created during a build are not followed. Folders such as node_modules and dist are listed but not searched inside. NOT FLAGGED is not a guarantee.
Static check of ignore rules and file contents. The global git excludes file, compose or CI build contexts, variables in COPY paths and pnpm or Yarn publish differences are not checked. NOT FLAGGED is not a guarantee.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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 5 days ago
Requires
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example projects include clearly fake, inert tokens and passwords (not-a-real-..., NOTREAL) for the scanner to find. They are never used.