wjgoarxiv Antigravity Swarm LSP
Use this skill when edits touch code that has language-server or compiler diagnostics.
- Identify the changed files and their language.
- Prefer project-native diagnostics:
npm test,tsc --noEmit,ruff,pyright,cargo check,go test, or the repo's configured checker. - Use symbol-aware rename/reference tools when available in the active harness.
- Treat hook diagnostics as early warning only; rerun the authoritative project command before completion.
- If a language server is unavailable, report the fallback command you used.
Diagnostic Triage
- Separate pre-existing diagnostics from diagnostics introduced by the current diff.
- Fix introduced diagnostics before broad refactors.
- When a diagnostic is caused by generated files, verify the generator or package output instead of hand-editing generated code.
- For renamed symbols, check imports, tests, docs examples, and package exports.
Fallbacks
If no language server is available, use the project-native static check:
- TypeScript/JavaScript:
npm test,npm run typecheck,tsc --noEmit, or configured lint. - Python:
pytest,ruff,pyright, orpython -m py_compilefor small scripts. - Rust:
cargo checkand targeted tests. - Go:
go test ./....
Report exactly which fallback ran.