pvs-studio
Run PVS-Studio static analysis on the project to find and fix bugs, security issues, and undefined behavior. Use proactively when code quality or security needs to be checked.
来源信息
- 仓库
- bivex/pvs-agent
- 最近来源活动
- 2026年3月4日 17:02
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 0
- 分支
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- pvs-studio
- description
- Run PVS-Studio static analysis on the project to find and fix bugs, security issues, and undefined behavior. Use proactively when code quality or security needs to be checked.
- context
- fork
- agent
- pvs-studio
Run PVS-Studio static code analysis on the current project. $ARGUMENTS
1. Assess the target project and determine the build system (Make, CMake, compdb, etc.).
2. Set up the environment to run PVS-Studio. If using CMake, generate `compile_commands.json` (`cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=On .`). If using Make, intercept compilation (`pvs-studio-analyzer trace -- make`).
3. Run the analysis using `pvs-studio-analyzer analyze -o pvs-studio.log -j4`.
4. Convert the output using `plog-converter`. Use `-t json` or `-t markdown` so you can easily read the results. For example: `plog-converter -a GA:1,2;OP:1,2 -t json -r . -o pvs-report.json pvs-studio.log`.
5. Review the converted analysis results (e.g., `pvs-report.json`) and summarize the critical bugs. Look specially for High (Level 1) and Medium (Level 2) certainty issues in General Analysis (GA) and Security (OP).
6. Present a clear summary of findings to the user.
7. Suggest or implement code fixes for the critical issues found by the analyzer.
在 GitHub 查看