agentleFS
Sign inStart free
accsoaccso/ai-context-mcp/.github/skills/ai-context-workflow/SKILL.md

ai-context-workflow

Skill2 starsChanged 34 days agoApache-2.0View on GitHub

Use for code context, file locations, or an architecture overview on the ai-context repository before writing or modifying code. Drives repo_structure, semantic_search, get_file, analyze_impact, and (when configured) resolve_symbol against the project-specific {project_key}-context MCP server that matches the user's question.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. accso/ai-monitoring★ 2100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the question is repo-wide or you are unsure, start with the project that owns the file path or module mentioned in the question.

    line 24
  2. Very specific:

    Read the returned summaries before requesting full files.

    line 34
  3. Very specific:

    Stop as soon as you have enough context — don't call every tool by default.

    line 60
  4. Very specific:

    If semantic_search finds nothing after one rephrase, say so instead of guessing.

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ai-context — Codebase Context Workflow

This skill covers every project indexed by ai-context in this repository. Each project is served by a separate MCP server named {project_key}-context.

  1. Pick the project. Choose the MCP server whose project best matches the user's question. Registered projects:

    MCP serverProjectURL
    ai-context-contextAI Contexthttp://localhost:7111/mcp
    If the question is repo-wide or you are unsure, start with the project that
    owns the file path or module mentioned in the question.
  2. repo_structure — call first on the chosen project for orientation (module map, directory tree). Per-file entries may show [hub]/[bridge] structural-role tags (derived from the import/call graph) — hubs warrant extra care before changing.
  3. semantic_search(query) — use technical identifiers, not prose (e.g. UserRepository authenticate, not "how do users log in"). Read the returned summaries before requesting full files. Each hit includes a why note (identifier match, vector similarity, keyword boost, or rerank) — use it to judge trustworthiness, not just the score.
  4. get_file — only if step 3 wasn't enough. Max 2 calls per query, max 3 files per call. Works for code and docs automatically.
  5. analyze_impact(symbol_name, direction, [file_path], [depth], [include_tests]) — before editing or removing a symbol, to see its callers/callees (blast radius) and which test files likely cover it. direction is callers, callees, or both. Pass file_path to disambiguate if the symbol name is not unique in the project.
  6. resolve_symbol(file_path, line, character, kind) — only if the project has lsp enabled for that language (not every project/language has this). Use for compiler-grade precision (kind=definition, references, or hover) when the heuristic call graph from analyze_impact or the results from semantic_search/get_file leave the exact declaration or call sites ambiguous. Higher cost than steps 2 to 5 — reach for it only when those are not enough, and skip it if the tool reports the language or project is not configured for it.

Some projects declare sources in ai-context config; if the answer likely lives in a related module (e.g. a frontend asking about a backend API), repeat the workflow against the source project.

Stop as soon as you have enough context — don't call every tool by default. If semantic_search finds nothing after one rephrase, say so instead of guessing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free