agentleFS
u7-u7u7-u7/dev-skills/skills/review/author-final-review/SKILL.md

author-final-review

Skill4 starsChanged 55 days agoNo licenceView on GitHub

当需要对一个或多个仓库中“单一指定作者”的最终态变更做全面 Bug 导向代码审查时使用。本技能基于 base..head 的最终代码状态审查,而不是逐个中间提交审查;适用于审查自己或他人的提交,但不适用于多人混合变更的整体审查。若作者、分支范围或应用范围缺失,先自动推断候选项并提出聚焦澄清问题。

The file

Show its rules and text

We split this skill into the rules it gives an agent

46 rules. About 0 are common, 35 are distinctive, and 11 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈35

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 11

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.