doc-ignorer

Generate a .geminiignore file that filters codebase noise while preserving signal folders.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Swear4/agent_rules --skill doc-ignorer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-ignorer
Source: https://github.com/Swear4/agent_rules/tree/main/agent-universal/skills/doc-ignorer
Command: npx skills add https://github.com/Swear4/agent_rules --skill doc-ignorer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes a codebase to define the scope for a structured scan and generates a .geminiignore to filter noise (configs, tests, assets) while preserving the signal (pages, routes, models, i18n) for KB documentation.

Core Features & Use Cases

  • Identify the project structure and noise signals to focus documentation on user-relevant features.
  • Produce a .geminiignore that excludes build outputs, dependencies, tests, and tooling while preserving essential UI and data signal folders.
  • Use Case: When starting a new project, run this skill to quickly generate a signal-focused ignore file for the documentation KB.

Quick Start

Run doc-ignorer on your codebase to generate a .geminiignore at the repository root.

Frequently Asked Questions about doc-ignorer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a .geminiignore file to filter codebase noise for documentation?

To generate a .geminiignore, analyze your codebase to identify signal patterns like pages, routes, and models, then exclude noise such as configs, tests, and assets to define a clean documentation scan scope.

What codebase patterns should I keep versus exclude when creating a .geminiignore?

When creating a .geminiignore, keep essential signal folders like pages, routes, models, and i18n, while excluding noise such as build outputs, dependencies, tests, and tooling configurations to focus documentation on user-relevant features.

How does a .geminiignore file improve KB documentation quality?

A .geminiignore improves KB documentation quality by filtering out codebase noise like assets and tests, ensuring the structured scan focuses strictly on essential signal patterns to produce relevant user-facing documentation.

Can I use this approach to define scan scope for an existing repository?

Yes, you can define scan scope for an existing repository by identifying its project structure and generating a ready-to-use .geminiignore at the repository root to filter noise and preserve essential UI and data signals.

What prerequisites are needed to scan a codebase and generate a .geminiignore?

The primary prerequisite is having access to the codebase so the tool can validate project structure, identify signal patterns, and output the .geminiignore file directly at the repository root.

Why does my documentation scan include unwanted config and test files?

Your documentation scan includes unwanted files because a .geminiignore is missing; generating one excludes configs, tests, and assets while preserving essential signals like pages and models for a focused KB scan.