Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Context Bootstrap: AI Codebase Awareness

    1

    A pre-flight context engine that indexes docs, git history, and active PRs to prevent contextually wrong code.

    $14.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Context Bootstrap: AI Codebase Awareness

    Context Bootstrap: AI Codebase Awareness

    Example session with this skill installed

    I need to add a date formatting utility for the new dashboard. I'm going to use date-fns since it's the standard.

    I don't have my terminal open, but here is the relevant context you need:

    [package.json]

    {
      "dependencies": {
        "dayjs": "^1.11.9",
        "express": "^4.18.2"
      }
    }
    

    [CONTRIBUTING.md]

    Guidelines

    • Do not add new dependencies without a team vote.
    • Use dayjs for all date manipulation. date-fns was explicitly removed in ADR-014 due to tree-shaking issues in our Vite setup.

    [src/utils/date.ts]

    import dayjs from 'dayjs';
    export function formatDate(date: string) {
      return dayjs(date).format('MMM D, YYYY');
    }
    

    Write the new utility for the dashboard.

    • Read your context and instructions
    • Compiled the context bootstrap

    Context loaded

    • Project: Express-based app with a new dashboard (Vite on the frontend, per ADR-014). I have not seen a README.
    • Relevant docs read: CONTRIBUTING.md (as pasted), package.json (as pasted)
    • Recent history: none found (no git log provided)
    • Existing implementations found: src/utils/date.ts exports formatDate(date: string), formatting as MMM D, YYYY via dayjs
    • Active work: none found (no open PRs or branches provided)
    • Constraints or conventions: use dayjs for all date manipulation; date-fns was removed in ADR-014 (tree-shaking issues with Vite); no new dependencies without a team vote
    • Gaps: I haven't read ADR-014 itself, other utilities in src/utils/, or the dashboard's actual date needs

    I found a contradiction, so I'm not using date-fns. Your CONTRIBUTING.md says date-fns was explicitly removed in ADR-014, and adding it would need a team vote. It also isn't in package.json. Instead, I'd extend the existing dayjs-based file, which adds no dependencies and follows the rule.

    Here's the utility, added to src/utils/date.ts alongside the existing formatDate:

    import dayjs from 'dayjs';
    import relativeTime from 'dayjs/plugin/relativeTime';
    
    dayjs.extend(relativeTime);
    
    type DateInput = string | number | Date | dayjs.Dayjs;
    
    // Existing function, unchanged
    export function formatDate(date: string) {
      return dayjs(date).format('MMM D, YYYY');
    }
    
    /** Date and time, e.g. "Mar 5, 2025, 3:42 PM" */
    export function formatDateTime(date: DateInput): string {
      const d = dayjs(date);
      return d.isValid() ? d.format('MMM D, YYYY, h:mm A') : '';
    }
    
    /** Compact form for dashboard tables/charts, e.g. "Mar 5" */
    export function formatShortDate(date: DateInput): string {
      const d = dayjs(date);
      return d.isValid() ? d.format('MMM D') : '';
    }
    
    /** Relative time, e.g. "3 hours ago" */
    export function formatRelative(date: DateInput): string {
      const d = dayjs(date);
      return d.isValid() ? d.fromNow() : '';
    }
    

    Notes

    • relativeTime ships with dayjs (dayjs/plugin/relativeTime), so it isn't a new dependency. I'd still check whether the plugin is already extended elsewhere, since dayjs.extend is global and calling it twice is harmless but redundant.
    • I returned '' for invalid dates rather than dayjs's "Invalid Date" string, which is friendlier for UI rendering. If the team prefers throwing or a placeholder like '—', that's a one-line change.
    • I left formatDate untouched so existing callers don't break.

    I didn't search for other date helpers, so a few things would help confirm this is the right shape:

    1. Does anything else in src/ (e.g. src/lib) already format dates?
    2. Which formats does the dashboard actually need? I guessed at the three above.
    3. Are there any open PRs touching src/utils/date.ts?

    If you do want date-fns, the path is a team vote plus a look at ADR-014, and I'm happy to draft that proposal.

    Your CONTRIBUTING.md

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

    About this skill

    Building code in a vacuum leads to duplicate utilities, violated architectural patterns, and conflicts with active work. This skill enforces a "context before action" protocol to ensure every code change is grounded in the project's actual state and history.

    What it does

    • Proactive Indexing builds a situational map of documentation, ADRs, and recent commits before any logic is written.
    • Dependency Mapping identifies existing implementations of functions or patterns to prevent code duplication.
    • History Analysis scans the last 50 commits to identify churning files, recent refactors, and previously reverted attempts.
    • Flight-Check Integration verifies active work in open PRs, issues, and branches to prevent merge conflicts.
    • Gap Identification explicitly lists what could not be verified, preventing confident but incorrect assumptions.

    How it works

    1. Map the Docs reads high-signal files like README.md, ARCHITECTURE.md, and docs/adr/ to understand project boundaries.
    2. Scan History executes git log commands to surface recent work and hotspots in specific directories.
    3. Search for Evidence uses targeted grep and find commands to locate existing symbols or similar implementations.
    4. Synthesize Findings outputs a standardized "Context Block" for user verification before proceeding with the main task.

    Frameworks & tools

    This skill utilizes standard Unix utilities like grep and find, the git CLI for history retrieval, and the gh CLI for GitHub issue and PR tracking.

    Why this beats prompting it yourself

    Standard prompts often cause agents to hallucinate that a pattern exists or to blindly create new files without checking for existing ones. This skill forces a rigorous retrieval-first workflow that prioritizes evidence over confidence, drastically reducing the cost of refactoring contextually wrong code.

    Use cases

    • Task Onboarding when starting a new ticket to ensure you aren't duplicating an open PR.
    • Session Resumption to quickly catch up on recent commits and architectural changes made by teammates.
    • Pre-flight Auditing to check if a planned implementation violates a previously recorded ADR.
    • Contextual Debugging to see if a bug was introduced in a recent refactor or a previously reverted fix.

    Known limitations

    Requires terminal access and CLI tools like git or gh to be installed. Performance depends on the presence of documentation files and clear commit histories.

    Requires git and grep/find utilities. Optimal performance requires gh CLI for PR/issue tracking. Scope is limited to the local repo and linked remote metadata.

    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

    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 7 days ago

    Requires

    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Listed7 days ago

    What's inside

    Frequently Asked Questions

    This skill acts as a pre-flight checklist for your AI agent, forcing it to scan documentation, git history, and active PRs before writing code. It prevents common issues like code duplication, architectural violations, and merge conflicts by grounding the agent in the project's real-time state.

    The skill is designed for any AI agent with terminal access and local file system permissions. It requires the `git` and `gh` (GitHub) CLI tools to be installed in the agent's environment to successfully index repository data and active PRs.

    Unlike general prompts, this skill enforces a strict 'retrieval-first' workflow using system-level tools. It eliminates hallucinations by requiring the agent to provide evidence from your codebase and ADRs before it is allowed to propose logic or changes.

    Your purchase includes the Context Bootstrap skill configuration, integration instructions for major AI agent platforms, and a guide on optimizing your repository's documentation for better indexing results.

    Context Bootstrap is highly effective for large or legacy repositories because it specifically identifies 'churning' files and recent refactors. By scanning the last 50 commits, it ensures the agent understands the momentum of the project, not just the static files.

    New in Technical Documentation