Superpowers Receiving Code Review
v1.0.0Use when receiving code review feedback - requires technical verification before implementing suggestions, with reasoned pushback when feedback is technicall...
⭐ 0· 95·0 current·0 all-time
by@axelhu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the SKILL.md: guidance for handling code review feedback. The skill requests no binaries, environment variables, or installs that would be out of scope for this purpose.
Instruction Scope
The runtime instructions explicitly direct the agent to read and verify feedback against the codebase (e.g., 'grep the codebase', '对照代码库现实检查', '引用工作的测试/代码'). That is appropriate for a code-review helper, but it implies access to repository files and history. The skill does not instruct contacting external endpoints or accessing secrets, and its scope is prescriptive (what to say/do).
Install Mechanism
There is no install spec and no code files. This instruction-only approach minimizes installation risk.
Credentials
No environment variables, credentials, or config paths are requested. The SKILL.md does not reference secrets or unrelated services.
Persistence & Privilege
always is false and the skill does not request persistent system presence or modify other skills. The default ability for the model to invoke the skill autonomously is unchanged; that is normal and not problematic here.
Assessment
This skill is coherent and appears safe: it mainly prescribes how to read, verify, and respond to code-review feedback and expects access to the codebase. Before enabling it, confirm the agent has only the intended repository/workspace access (read/write as appropriate) and that your team's communication norms match the skill's strict discouragement of polite acknowledgements—some teams expect explicit thanks or different phrasing. If you want stricter controls, restrict the skill's invocation to specific repositories or require manual invocation rather than autonomous invocation. If you need a different tone/behavior, request a variant that preserves politeness or makes the phrasing configurable.Like a lobster shell, security has layers — review code before you run it.
latestvk978mtdqqwjfzbz43pckm4yrqx83mat6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.