generate-compile-commands Skill
Generate compilecommands.json (clang compilation database) for the C++ language server. Covers MSBuild (.sln, .slnx, .vcxproj) via microsoft/msbuild-extractor-sample and CMake projects via CMAKEEXPORTCOMPILECOMMANDS. Use whenever the user asks to "regenerate compile commands", "regenerate the project", "reload the proj Published by microsoft in cpp-language-server.
What is generate-compile-commands Skill?
Generate compilecommands.json (clang compilation database) for the C++ language server. Covers MSBuild (.sln, .slnx, .vcxproj) via microsoft/msbuild-extractor-sample and CMake projects via CMAKEEXPORTCOMPILECOMMANDS. Use whenever the user asks to "regenerate compile commands", "regenerate the project", "reload the proj Published by microsoft in cpp-language-server. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Database workflows
- Writing
- Database workflows use cases
- Writing use cases
Technical details
- Install or run with Copy skill directory
When to use generate-compile-commands Skill
- Use it for database workflows.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/cpp-language-server
- Skill file: plugins/cpp-language-server/skills/generate-compile-commands/SKILL.md
What it does
Generate compilecommands.json (clang compilation database) for the C++ language server. Covers MSBuild (.sln, .slnx, .vcxproj) via microsoft/msbuild-extractor-sample and CMake projects via CMAKEEXPORTCOMPILECOMMANDS. Use whenever the user asks to "regenerate compile commands", "regenerate the project", "reload the proj
Skill instructions
Generate compilecommands.json The C++ language server needs a compilecommands.json (clang compilation database) to understand a project. How you produce one depends on the build system: CMake can export it directly, MSBuild needs an external extractor. Always regenerate compilecommands.json when this skill runs, even if one already exists for the project. For MSBuild, write it to .mscppls\compilecommands.json at the workspace root (the examples below do this); mscppls auto-discovers any compilecommands.json within the workspace, so no cpp-lsp.json is required. Add .mscppls/ to .gitignore so it does not get committed. mscppls hot-reloads the file content; /restart is only needed after changing the plugin's lsp.json or the workspace cpp-lsp.json (those are read once at LSP startup). CMake projects CMake writes compilecommands.json itself; no external extractor needed. Enable it at configure time: bash cmake -S . -B build -DCMAKEEXPORTCOMPILECOMMANDS=ON cmake --build build Or persist it i
Explore related resources
Frequently asked questions
What is generate-compile-commands?
generate-compile-commands is a open-source AI agent skill with Copy skill directory. Generate compilecommands.json (clang compilation database) for the C++ language server.
Who is generate-compile-commands best for?
generate-compile-commands is best for reusing agent instructions, scripts, and references, database workflows, writing workflows.
How do I install generate-compile-commands?
Install or run generate-compile-commands using Copy skill directory. Check generate-compile-commands for the latest setup command.
Is generate-compile-commands actively maintained?
generate-compile-commands may need a closer maintenance check before production use.
Auto-fetched from GitHub.
