workflow-lsp
Skill1 starsChanged 6 months agoMITView on GitHub
Use lsp_find_references, lsp_go_to_definition, and lsp_diagnostics when navigating cross-file symbol relationships or checking for type errors after edits. Prefer LSP over grep for symbol lookup — it is exact (compiler-grade) and ~50ms vs tens of seconds, and catches cross-file errors immediately after an edit. Trigger when finding a symbol's definition/callers or validating an edit touched no other file.
In this repository33 other files it gives its agents.
- skill-process-gotchasSkill
- workflow-cache-disciplineSkill
- workflow-codegraphSkill
- workflow-conductorSkill
- workflow-context-condenserSkill
- workflow-context-hygieneSkill
- workflow-criticSkill
- workflow-deadline-disciplineSkill
- workflow-deep-researchSkill
- workflow-done-definitionSkill
- workflow-edit-formatSkill
- workflow-effort-routingSkill
- workflow-escalateSkill
- workflow-execute-from-planSkill
- workflow-filesystem-offloadSkill
- workflow-learn-frameworkSkill
- workflow-long-running-processesSkill
- workflow-memory-curationSkill
- workflow-plan-contractSkill
- workflow-plan-firstSkill
- workflow-planSkill
- workflow-quality-barSkill
- workflow-repomapSkill
- workflow-retrieve-before-actSkill
- workflow-spec-drivenSkill
- workflow-stuck-detect-resetSkill
- workflow-stuckSkill
- workflow-subagent-isolationSkill
- workflow-subtask-loopSkill
- workflow-task-finishSkill
- workflow-task-startSkill
- workflow-tool-selectionSkill
- workflow-verify-enhancedSkill
The file
Files
workflow-lsp
<!-- TRIGGERS WHEN: looking up a symbol's definition/references, or checking type errors after an edit -->Compiler-grade symbol intelligence (Serena language-server backend, via mcp-lsp). Prefer LSP over grep for symbol work — grep matches text and misses scope/imports; the language server resolves the actual symbol.
| Tool | Use it to |
lsp_find_references(name_path, relative_path) | find every CALLER of a symbol before changing its signature |
lsp_go_to_definition(name_path) | jump to the real signature/body instead of guessing or grepping |
lsp_diagnostics(relative_path) | immediately after editing a file, catch type errors / undefined names without waiting for the verify gate |
lsp_find_symbol(name_path) | locate a function/class/method by name across the project |
Discipline
- After every non-trivial edit, run
lsp_diagnosticson the changed file — this is the tight feedback loop (catch the cross-file type error now, not at verify time). - Before changing a signature / renaming, run
lsp_find_referencesto see the full blast radius. relative_pathis relative to the project root; calllsp_activate_projectwhen you switch to a different repo so the language server re-indexes it.
Degrades gracefully: if the backend/language server is down the tool returns a clear
error — fall back to search_code (RAG) or grep.
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
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.