Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agents.gitignore
Audit and adopt standardized gitignore rules to separate private working records from public documentation.
$3
.gitignore
Example session with this skill installed
Audit the current project for ignore rule gaps and separate my private dev notes in docs/ from the public API specs.
- Read your context and instructions
- Compiled the gitignore
I have audited the repository's ignore configuration and identified several issues where private working notes are currently exposed or improperly classified. ## Audit Report: Git Visibility & Documentation | Finding Type | Path/Pattern | Status | Recommendation | | :--- | :--- | :--- | :--- | | **Tracked Private** | `docs/internal/roadmap_2024.md` | EXPOSED | Move to ignored private path and untrack. | | **Broad Ignore** | `docs/` | OVER-INCLUSIVE | Lift ignore; specifically ignore `.private/` and `.notes/`. | | **Missing Pattern** | `*.log`, `.env.local` | RISK | Add to `.gitignore` to prevent accidental commits. | | **Visibility Conflict** | `dist/` | TRACKED | Files in `dist/` are currently tracked despite ignore rule. | ### Proposed Changes 1. **Merge Asset**: Add standard environment and OS-level ignore patterns from the reusable asset. 2. **Refactor Docs**: Move private files from `docs/` to `docs/.private/` while keeping `docs/api-spec.md` public. 3. **Index Cleanup**: Generate the commands to remove already tracked private files from the Git index. **Next steps** - Run `gitignore apply` to merge the standardized patterns and relocate private notes. - Review the `docs/` structure to ensure public links to API specs remain functional. - Execute `git rm --cached` on the identified tracked-private files to respect new ignore rules.
Connects securely to your tools. The creator never sees your data.
About this skill
Loose .gitignore rules lead to leaked secrets, bloated repositories, and private working notes accidentally becoming public. This skill audits your existing ignore patterns and implements a structured strategy to separate private records from public product documentation.
What it does
- Standardize patterns by merging a reusable, battle-tested gitignore asset into your project.
- Isolate documentation by lifting broad doc ignores and classifying records into public and private destinations.
- Validate visibility using a Node-based verifier to ensure private paths are actually untracked.
- Detect tracked secrets by identifying private material that was committed before the ignore rule existed.
- Preserve custom rules by merging project-specific exclusions instead of blindly overwriting your configuration.
How it works
- Inspection of existing ignore files, Git status, and project structure to classify files.
- Audit mode to report visibility findings and tracked-private issues without modifying files.
- Adoption workflow to merge the template, move private records, and update
.gitignore. - Verification via
check-ignore.mjsto confirm the visibility contract is met post-change.
Frameworks & tools
This skill requires Git in the target project. The read-only verifier script requires Node 22+ for execution.
Why this beats prompting it yourself
Generic prompts often result in a generic .gitignore that deletes your specific build rules or fails to handle files already in the Git index. This skill follows a specific adoption guide that treats documentation as a first-class citizen, ensuring your internal notes stay out of the public repo while maintaining valid links.
Use cases
- Clean up a messy root directory by moving internal notes to ignored paths.
- Audit a repository to find files that should be ignored but are currently tracked.
- Implement a standardized gitignore across a multi-repo organization.
- Safely extract public API contracts from internal-only documentation folders.
Known limitations
This skill is not for secret scanning, repository history cleanup, or full documentation content audits. It requires a local Git installation to function.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed 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 scanned
Verified clean 6 days ago
- Passed all security checks, Safe to install