williamlimasilva/codebase-memory-mcp
skills/codebase-memory-mcp/SKILL.md
Use when a configured codebase-memory-mcp server can assist with graph-backed code discovery, architecture orientation, symbol lookup, callers and callees, dependency or data-flow tracing, impact analysis, unfamiliar modules, or an explicit Codebase Memory request.
tools
Updated Jul 22, 2026
$ install --global
skillsauthnpx skillsauth add williamlimasilva/.copilot codebase-memory-mcpInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 22, 2026, 2:19 AM144.6s1 file scanned
SKILL.md
- name:
- codebase-memory-mcp
- description:
- Use when a configured codebase-memory-mcp server can assist with graph-backed code discovery, architecture orientation, symbol lookup, callers and callees, dependency or data-flow tracing, impact analysis, unfamiliar modules, or an explicit Codebase Memory request.
Codebase Memory MCP
Use the configured Codebase Memory graph as a discovery accelerator, not as the sole source of truth. Confirm graph-derived conclusions with source snippets or local files before editing code or making strong claims.
Workflow
- Discover the Codebase Memory tools exposed by the current MCP client; clients may prefix or rename tool namespaces.
- Call
list_projectswhen available and use the exact indexed project name. If the repository is not indexed, continue with local exploration or ask before callingindex_repositorywhen graph access is important. - Before branch-sensitive or edit-sensitive conclusions, use
index_statusordetect_changeswhen available. After a branch switch, assume the index may be stale until checked. If freshness cannot be established, disclose that limitation and verify locally. - Use
get_architectureonce for orientation in an unfamiliar repository or subsystem. Do not repeat it for narrow follow-up questions. - Use
search_graphfor definitions, implementations, routes, classes, interfaces, callers, and related symbols. Prefer a natural-language query for discovery and a name or qualified-name pattern for known symbols. Narrow by label or path, set a result limit, and paginate or reduce scope when the response reports more results. - Use
search_codeor normal repository search for literal strings, configuration keys, test identifiers, error messages, and non-code files. Do not turn a precise text lookup into a broad graph query. - After graph search, use
get_code_snippetwith the returned qualified name. If source snippets are unavailable, open the local file before relying on the result. - Use
trace_pathfor callers, callees, dependency paths, data flow, cross-service paths, and impact analysis. Include tests only when test coverage is part of the question. - Use
get_graph_schemabeforequery_graph. Reserve custom queries for multi-hop or aggregate questions that simpler tools cannot answer, and applyLIMITor the tool's row limit. - When graph and checked-out source disagree, treat source as current and report likely index drift.
Safety and Fallbacks
- Do not install Codebase Memory or another third-party skill from this workflow.
- Do not call
delete_project, ingest traces, update ADRs, or index a repository unless the user explicitly requested or approved the action; announce it before execution. - Fall back to normal repository exploration when the MCP server, project, index, or required capability is unavailable; do not invent tool results or stop a task that can be completed safely without the graph.
Related Skills
williamlimasilva/workshop-create
tools
VerifiedTrustedCommunity
Create a new workshop or use an existing directory as one. Handles two paths: (A) use an existing local directory the operator points at, or (B) create a new private GitHub repo in the signed-in account. Never creates a repo inside another repo.
SKILL.mdUpdated Jul 22, 2026
williamlimasilva/vcpkg
development
VerifiedTrustedCommunity
Guide for setting up vcpkg in C++ projects, managing dependency versions, and cross-compiling. Covers manifest initialization, CMake and Visual Studio integration, classic-to-manifest migration, version pinning, baselines, overrides, triplets, and cross-compilation. Use when a user is working with vcpkg project setup, installation, version management, or cross-platform builds. For specialized tasks, additional references cover custom registries and overlay ports (references/registries.md), CI/CD and binary caching (references/ci.md), and troubleshooting and dependency lifecycle (references/troubleshooting.md).
SKILL.mdUpdated Jul 22, 2026
williamlimasilva/signal-write
testing
VerifiedTrustedCommunity
Emit structured agent signals — hands-up, blocked, done, checkpoint, partnership. Signals are written as JSON to .signals/ for dashboard consumption and noted in the journal for persistence.
SKILL.mdUpdated Jul 22, 2026
williamlimasilva/markstream-install
development
VerifiedTrustedCommunity
Install and configure Markstream streaming Markdown renderers for Vue, React, Svelte, Angular, Nuxt, and Vue 2 applications. Use for package selection, minimal peer dependencies, CSS order, SSR boundaries, streaming mode, and renderer setup.
SKILL.mdUpdated Jul 22, 2026