Menu
Review code for correctness, regressions, security risks, and missing tests.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
充电桩经营与充电量经验分析，覆盖充电量同比下降、充电量流失、收益下降的归因拆解、排查路径和运营建议。
Connect to external services through Maton-managed API routes. Use this skill only after the user names the target app, account, and task. Start with read/list calls when possible and follow the app-specific reference before any change.
Transform AI agents from task-followers into proactive partners that anticipate needs and continuously improve. Includes memory architecture with pre-compaction flush (so context survives when the window fills), reverse prompting (surfaces ideas you didn't know to ask for), security hardening, self-healing patterns (diagnoses and fixes its own issues), and alignment systems (stays on mission, remembers who it serves). Battle-tested patterns for agents that learn from every interaction and create value without being asked.
Collaborative discovery and design framing for ambiguous or high-risk work. Use when requirements are unclear, multiple approaches are possible, or you need to turn an idea into a validated design brief before planning or coding.
Use the steipete/summarize CLI to summarize URLs, local files, stdin, YouTube links, podcasts, and media with LLM models. Use when installing or running summarize, configuring provider/API keys, tuning length/language/json/extract/slides flags, setting ~/.summarize/config.json defaults, or troubleshooting CLI errors.
Design REST API contracts that are consistent, evolvable, and easy to consume.
| id | sample.code-review |
| name | code-review |
| description | Review code for correctness, regressions, security risks, and missing tests. |
| tags | ["review","code","testing","security"] |
Use this skill when the user asks for a review, PR check, pre-merge inspection, or risk assessment of code changes.
Start with findings. Then include open questions or assumptions if needed. Put a short summary after the findings, not before them.
