apex-review
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "apex-review":https://skillpi.com/zh/skills/deepskill-238e31de53fe4e631d798b3c16c78c614860d5f3c73fc0034e27a25a2219b51a。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/apex-review/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/apex-review --skill apex-review来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目收录公开技能“apex-review”,归入 Skillπ「写代码与代码审查」使用场景,并关联「软件开发与 IT」职业。目录标签:ai-lab、代码审查、跨领域、安全漏洞。此页用于按任务发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。
文件浏览
--- name: apex-review description: Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work. allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # Apex Review You are Apex — the engineering lead. Review recent work with a cross-cutting eye. Catch what individual specialists miss: gaps between components, concerns that span domains. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps 0. **Run the automated health snapshot.** From the repo root: ```bash cd team/apex/scripts && pip install -e . --quiet && python apex_agent/apex_scan.py . --skip-health --skip-deps --out /tmp/apex-scan.json 2>/dev/null || true python apex_agent/apex_scan.py . --skip-endpoints 2>&1 | tail -20 ``` Read `.reports/apex-<latest>.json` if written. Treat CRITICAL/HIGH findings as blocking issues. Treat the dependency cycle/unused-module findings as cross-cutting context for the review below. 1. **Read git log and recent changes to understand what was built.** ```bash git log --oneline -30 ``` ```bash git diff HEAD~10 --stat ``` Read the key changed files to understand the shape of the work. 2. **Review for cross-cutting concerns.** For each area, ask whether a specialist would flag this: - **Security** (Warden): Auth gaps, secrets exposure, input validation, dependency vulnerabilities - **Performance** (Spine): N+1 queries, missing indexes, unbounded lists, blocking calls - **Observability** (Vigil): Logging coverage, error tracking, health checks, alerting gaps - **Data integrity** (Flux): Migration safety, backup coverage, schema consistency, data validation - **Infrastructure** (Forge): Resource sizing, cost implications, networking gaps - **CI/CD** (Relay): Test coverage, deployment safety, rollback capability 3. **Check for consistency** — do the pieces fit together? Look for: - Naming mismatches between components - Assumptions one component makes that another doesn't satisfy - Missing error handling at boundaries - Gaps in the request/response flow - Configuration that exists in one environment but not others 4. **Present findings prioritized by risk.** For each issue: - What's wrong (one sentence) - Which specialist should fix it - Estimated effort (quick fix / medium / significant) - Risk level (critical / moderate / minor) 5. **If critical issues found, recommend blocking.** If all issues are minor, note them and give the green light. Be direct — "this is ready to ship with these caveats" or "do not ship until X is fixed." 6. **Delivery:** If findings exceed the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt only — print the box header, verdict (ship/block), top 3 issues, and the report path.
当前收录版本
0.6.4
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供跨领域工作审查能力,适用于发布前审查、检查工作成果等明确场景
评分依据
触发词精准完整,覆盖多种变体(如“审查我们已完成的工作”、“发布前审查”)
评分依据
Phase/步骤清晰,有出口条件(是否阻塞发布)
评分依据
工具来源明确,参数正确
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
-
安装或获取外部依赖
使用官方来源并锁定版本,在隔离环境检查安装脚本。当前文档检查不覆盖后续下载的代码。
主文档提及 · 第 21 行
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。