Safe code reviewer
Skill Gowrav-M/agent-skillguard/examples/skills/safe-code-reviewer
Policy-as-code admission controller for AI agent skills and MCP tools. SkillBOM, lockfiles, and supply-chain baselines.
npx -y skills add Gowrav-M/agent-skillguard --skill safe-code-reviewerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Read-only code review workflow for local repositories.
SKILL.md
0.4 KB, 61 tokens by cl100k_base, as published. Nobody here has run it
safe-code-reviewer
Review local source files and git diffs. Report correctness, security, and test gaps.
Rules
- Read files and git history only.
- Do not write files, run installers, or contact external services.
- Keep findings grounded in file paths and line references.
Gives 0 of the 12 instructions most code review skills give in 61 tokens
Counted across 610 of the 674 authors here whose files we hold, read 2026-08-06
- push back with technical reasoning if wrongin 60 of 610, across 24 files
- ask for clarification on unclear itemsin 51 of 610, across 16 files
- fix critical issues immediatelyin 45 of 610, across 29 files
- implement one item at a timein 45 of 610, across 11 files
- group findings by severityin 44 of 610, across 43 files
- verify feedback against the codebasein 42 of 610, across 8 files
- dispatch a code reviewer subagentin 39 of 610, across 23 files
- fix important issues before proceedingin 37 of 610, across 22 files
- test each fix individuallyin 35 of 610, across 7 files
- reply in github comment threadsin 33 of 610, across 5 files
- check for security vulnerabilitiesin 31 of 610, across 27 files
- factualize corrections without over-explainingin 30 of 610, across 2 files
Said here and by no other author read
- review local source files
- report correctness issues
- report security issues
- report test gaps
- read files and git history only
- ground findings in file paths
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.