alexbruno/dev-skills

codebase-indexing

Index, synchronize, and query a project's codebase using CodeGraph and Repomix.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/alexbruno/dev-skills --skill codebase-indexing

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Codebase Indexing (CodeGraph + Repomix)

Maintain a dual indexing setup and use these indexed artifacts as your primary context to understand the project's full structure, architecture, and engineering before scanning individual files or running brute-force searches:

  • CodeGraph (.codegraph/) as the primary source for structural symbol lookup, call paths, and dependency graphs.
  • Repomix (repomix-output.md) as the primary single-file Markdown snapshot of the repository's layout and implementation.

Always check whether each index already exists before running commands: initialize when missing, and sync/update when present.

1. CodeGraph

Pre-flight Check

Before running any CodeGraph command, verify that the codegraph executable is available in the environment (command -v codegraph).

  • If `codegraph` is NOT installed:
  • Alert the user immediately that CodeGraph indexing cannot be executed because the codegraph executable is missing from the environment.
  • Provide clear installation and setup instructions:
bash
    # Install globally via npm (or run `npx @colbymchenry/codegraph` for interactive setup)
    npm install -g @colbymchenry/codegraph

    # Optional: configure MCP / AI agent integration
    codegraph install

    # Initialize and index the project
    codegraph init
    codegraph index
  • Do not silently ignore the missing binary; continue with Repomix (if available) and note that CodeGraph remains unindexed until installed.

Check & Initialize vs. Sync

Check if .codegraph/ exists at the repository root:

  • If `.codegraph/` does NOT exist — initialize and build the graph database:
bash
  codegraph init
  codegraph index
  • If `.codegraph/` already exists — always run incremental synchronization:
bash
  codegraph sync

Do not re-run codegraph init or a full codegraph index when .codegraph/ is already present, unless the database is corrupted or major structural resets require a rebuild.

Querying CodeGraph

Reach for CodeGraph before running brute-force grep/find across the codebase:

  • MCP tool (when available): call codegraph_explore with symbol names, file paths, or architectural questions.
  • CLI: run codegraph explore "<symbol names or question>".

2. Repomix (Markdown Priority)

Always prioritize Markdown (--style markdown) for Repomix outputs so the snapshot is readable by both humans and LLMs. Always invoke Repomix via npx -y so it executes reliably even when not installed globally and without interactive prompts.

Check & Create vs. Update

Check if a Repomix Markdown file (e.g., repomix-output.md, or the output path configured in repomix.config.json) exists:

  • If it does NOT exist — create it in Markdown format:
bash
  npx -y repomix --style markdown -o repomix-output.md
  • If it already exists — re-run the update command to synchronize it with the current codebase:
bash
  npx -y repomix --style markdown -o repomix-output.md

(If `repomix.config.json` is present and already configured with `"style": "markdown"`, running `npx -y repomix` updates the configured output file directly.)

3. Maintenance & Verification

  1. Keep indexes fresh: Run codegraph sync and update the Repomix Markdown file after significant code changes, branch switches, or merges.
  2. Respect repository hygiene: Check .gitignore before committing generated .codegraph/ or repomix-output.md artifacts—ignore them unless the project explicitly tracks them in version control.
  3. Verify: Confirm .codegraph/ responds to codegraph explore and repomix-output.md (or the configured .md file) reflects the latest file tree.
from this repository

More skills

All skills
alexbruno
Community

architect-worker

Role-based multi-agent software engineering pattern separating high-level architecture, specification, planning, and code review (Architect) from focused code implementation and verification (Worker). Use this skill whenever assigned the Architect or Worker role (in any language), or when coordinating work between planning/review agents and implementation agents via workflow/.

1h installs
1
GitHub stars
0
Updated
Nov 13
alexbruno
Community

changelog-management

Maintain and update a standardized root CHANGELOG.md following Keep a Changelog and Semantic Versioning. Use this skill to initialize or update changelog entries, categorize changes, prepare release cuts, and proactively prompt the user when notable changes warrant updating the changelog.

1h installs
1
GitHub stars
0
Updated
Nov 13
alexbruno
Community

code-review

Perform structured, multi-dimensional code reviews aligned with the spec-driven-workflow (workflow/SPEC.md, workflow/PLAN.md, workflow/REVIEW.md). Use this skill after implementing a feature or bug fix, before merging a PR, or when reviewing changes written by another agent or human.

1h installs
1
GitHub stars
0
Updated
Nov 13
alexbruno
Community

code-simplification

Simplify code for human readability, clarity, and directness without changing behavior. Use this skill after implementing a feature, during refactoring, or when addressing code review feedback—especially when code feels over-engineered, deeply nested, or takes unnecessary detours to do simple things.

1h installs
1
GitHub stars
0
Updated
Nov 13