Ctx ignore
Agent skills (open standard) for the bookends of the agent loop: context assembly, decision review, and work-shaping outputs. Works with Claude Code and any Agent Skills harness. Ships its own adoption and value measurement.
npx -y skills add arniesaha/ctxops --skill ctx-ignoreAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
WHEN an agent keeps reading noise (node_modules, lockfiles, build output, generated code, fixtures) or a repo needs ignore files for AI tools. Triggers: 'generate a claudeignore', 'keep the agent out of X', 'my agent wastes context on generated files', 'set up ignore files', new repo onboarding. OUTPUT: a ranked noise report, an annotated .contextignore as source of truth, and tool-specific ignore files (.claudeignore, .cursorignore, .copilotignore, .windsurfignore). PAIR BEFORE: ctx-pack (exclude noise before assembling context). NOT FOR: choosing what to load for one task (use ctx-pack), .gitignore hygiene alone.
SKILL.md
2.4 KB, as published. Nobody here has run it
ctx-ignore
Decide what an agent should never read, once, instead of paying for the noise on every request. The other half of context assembly is context exclusion.
Workflow
- Walk the repo tree, respecting
.gitignore. Note file sizes. - Categorize noise candidates against
patterns.mdin this skill's directory (dependencies, lockfiles, build output, generated code, binaries, test artifacts, IDE/OS noise). Red entries always exclude; yellow entries (test files, migrations) need user confirmation. - Score each remaining candidate by context cost versus usefulness: large and mechanically produced ranks highest.
- Show a ranked report with a one-line reason per entry. Get confirmation before writing anything.
- Write
.contextignoreas the annotated source of truth (grouped, commented, dated header), then derive the tool-specific files the user wants:.claudeignore,.cursorignore,.copilotignore,.windsurfignore. - If existing ignore files are present, merge additions under a marked section. Never clobber hand-written entries.
Output Shape
- Ranked noise report: path, size, category, one-line reason
.contextignore(source of truth)- Tool-specific ignore files derived from it
- Skipped-on-purpose list: things that looked like noise but stay readable, with reasons
Rules
- Never exclude source, docs, or config that shapes runtime behavior, even when large.
- Lockfiles are noise for reading but load-bearing for reproducibility: exclude from agent context, never delete.
- When unsure whether a directory is generated, check for a generator config or header comment before excluding it.
- Report first, write second. No silent writes.
- Keep entries as directory or glob patterns, not hundreds of individual files.