skills/staged-review-validator/SKILL.md
Validate staged-changes-review findings with evidence-based verdicts and minimal-fix guidance. Use when you need to confirm whether each reported issue is valid and actionable.
npx skillsauth add adonis0123/adonis-skills staged-review-validatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
用于对已有审查报告做二次验证,不负责重新发起完整扫描。
staged-changes-review 结果,想确认每条问题是否真实成立staged-changes-review 文本(至少包含问题描述)如果用户没有粘贴审查结果:
references/output-template.md)git diff --cached从用户提供的报告提取每条问题:
对每条问题进行核验:
可使用但不限于以下命令:
git diff --cached
rg -n "关键符号" <path>
sed -n '<start>,<end>p' <path>
git show HEAD:<path>
每条问题只能输出以下三种之一:
成立:证据直接支持问题描述不成立:证据与描述冲突,或问题已修复待确认:证据不足(路径/行号缺失、上下文不完整等)成立 且风险为中/高:需要修改成立 且风险低:建议修改不成立:不需要修改待确认:暂不修改,先补充信息先给总览,再给逐条裁决。
结尾给出编号式“可执行下一步”。
staged-changes-review:发现候选问题staged-review-validator:验证候选问题是否真实成立串联时,后者不重复完整扫描逻辑,重点做证据核验与裁决。
references/verification-rubric.md:裁决标准、证据优先级、置信度映射references/output-template.md:固定输出模板与示例development
Use this skill when the user wants to set, write, or use a goal or /goal that makes a coding agent keep working until a verifiable done condition is met. This skill configures the autonomy and stopping contract for Codex, Claude Code, or portable agent prompts; it does not perform the underlying task. Trigger on requests like 'should I set a goal?', 'set up a durable goal', 'give me a /goal prompt', 'keep refactoring until tests pass', 'I am stepping away, have the agent finish this', or goal prompts for migrations, refactors, ports, spec implementations, eval loops, backlog cleanup, or multi-checkpoint work. Do not use for single quick edits, running tests once, OKR/scrum goal questions, recurring reminders, or token-budget settings.
testing
Create safe Git feature or hotfix branches with concise names. Use this whenever the user asks to create a branch, start work on a new feature or fix, wants a `feat/...` or `hotfix/...` branch name, asks for a short branch slug from a task description, or wants help before beginning local Git work. Default to recommending the branch name and command first, then create only after user confirmation. Do not push, commit, rebase, or create PRs.
tools
Use when the user's pain is "adding/removing one more X means editing N files" and X is a recurring variant kind: popup, banner, modal, ad slot, payment method, AI model/tool, form field type, connector, sub-site, command, menu item, agent, extension point, or data source. Use when they want to design, refactor, review, name, or explain a pluggable mechanism using registry, interface/trait contract, runtime core, and convention folders; mention pluginize, pluggable, plugin architecture, extension point, registry pattern, or extensibility. Use when explaining the first-principles rationale, DDD/SOLID/OCP mapping, or industry analogies behind that structure. Use for cross-stack mapping to VSCode contributes, Webpack/Vite plugins, Rust/Tauri connectors, Python entry_points, or cargo features. Skip one variant's internals/styles/hooks/copy/bugs, and skip register/registry meaning DI container, user signup, or package registry.
development
Use BEFORE heavier workflow skills when route choice matters. Route creative work without a design doc/spec to Brainstorm; destructive or hard-to-reverse work to Discuss; unresolved decisions, Plan/Full fan-out, ship checks, unclear bugs, and fresh-eyes fix-then-re-review need this gate. Skip single-line read-only lookups, pure typo/formatting edits, trivial safe one-line fixes, and clearly safe named-skill requests. Outputs Route, Runtime skill, Fallback alias, and Execution path.