feedback no duplicate docs

    1

    Enforce a single source of truth by preventing duplicate tracking, TODO, and checklist documents in your repository.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    feedback no duplicate docs

    Example session with this skill installed

    Create a list of verification steps for the upcoming production deployment to track our progress.

    • Read your context and instructions
    • Compiled the feedback no duplicate

    I have checked the repository for existing tracking documents and found tasks/CHECKLIST.md. Instead of creating a new file, I have added the deployment verification steps as a new section in the existing checklist to maintain a single source of truth.

    Updated tasks/CHECKLIST.md

    
    # Project Checklist
    
    ## Existing Tasks
    - [x] Configure CI/CD pipeline
    - [x] Set up staging environment
    
    ## Deployment Verification (New)
    - [ ] Verify SSL certificate expiry on production
    - [ ] Run smoke tests against the load balancer endpoint
    - [ ] Check Prometheus alerts for 5xx spikes
    - [ ] Validate database migration version in RDS
    - [ ] Confirm CDN cache invalidation completion
    

    Next steps

    • Review the new Deployment Verification section in tasks/CHECKLIST.md.
    • Let me know if you prefer these steps to be in a dated version instead (e.g., REGRESSION_2026_06_20.md).
    • I can add links to this section from your README.md for quicker access.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Repo bloat and document drift happen when agents create new files for tasks that already have a home. Parallel tracking documents lead to outdated information, lost context, and a fragmented source of truth. This skill forces a "search-before-write" workflow to ensure checklists, TODOs, and roadmaps stay consolidated.

    What it does

    • Prevents duplication by identifying existing tracking files before a new one is initialized.
    • Consolidates tracking by preferring Edit operations on existing .md files over creating new ones.
    • Automates discovery using targeted glob patterns for common document types like checklists, bug logs, and roadmaps.
    • Self-corrects misses by providing a recovery flow to migrate content and delete redundant files if a duplicate was already created.

    How it works

    1. Search phase triggered before any .md write in the repo root, tasks/, or docs/ directories.
    2. Analysis phase to determine if the new content is orthogonal or belongs in an existing candidate file.
    3. Consolidation phase where the agent extends the existing document section or asks the user for the authoritative file.
    4. Cleanup phase to delete duplicates and update cross-references if a miss occurs.

    Frameworks & tools

    Works with any repository structure using Markdown for documentation. Optimized for agents with filesystem access tools like Glob, Edit, and Write.

    Why this beats prompting it yourself

    Generic prompts often fail to check the full directory tree before generating output, leading to TODO_v2.md or REGRESSION_NEW.md clutter. This skill encodes specific search heuristics and a "Single Source of Truth" logic that enforces repository hygiene automatically.

    Use cases

    • Adding deploy verification steps to an existing project checklist.
    • Appending new bugs to a central BUG.md instead of creating a new task file.
    • Updating an existing sprint roadmap with deferred items.

    Known limitations

    Does not apply to genuinely unique artifacts with a different audience or angle. Requires the agent to have filesystem search capabilities.

    Requires agent filesystem access. Does not block creation of genuinely unique documents with different audiences or angles.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 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

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 28 days ago

    • Free with an Agensi account

    Permissions

    Write Files
    Listed28 days ago

    What's inside

    Frequently Asked Questions

    It prevents 'document drift' by enforcing a search-before-write workflow, ensuring that new tasks, bugs, or roadmap items are appended to existing files rather than creating fragmented duplicates like TODO_v2.md.

    This skill is compatible with any AI agent that has filesystem access (specifically Glob, Read, and Write capabilities) and works across any repository using Markdown for documentation.

    While optimized for common locations like the root, `/docs`, and `/tasks` folders, the skill's logic can be applied to any directory where you want to maintain a single source of truth for tracking documents.

    The skill includes a recovery flow that identifies the redundancy, migrates the new content into the original authoritative file, and deletes the duplicate to restore repository hygiene.

    You receive the core logic patterns and heuristic workflows that you can import into your agent's environment, along with documentation on how to integrate it with your agent's existing filesystem tools.

    New in Code Quality & Review