agentleFS
BanKnightBanKnight/claude-template/.claude/skills/implement-change/SKILL.md

implement-change

Skill0 starsChanged 5 months agoNo licenceView on GitHub

按 `.workflow/changes/<change-id>/tasks.md` 执行实现并更新任务状态。用户要求开始实现、继续实现或完成某个 change 时使用。

  • Other versions16 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 16

    1. pnpm/pnpm★ 37ksame name
    2. verdaccio/verdaccio★ 18ksame name
    3. Codagent-AI/agent-skills★ 31same name
    4. manhds82/claude-code-anyllm★ 16same name
    5. taljeon/plzdo★ 9same name
    6. Remote-Arc/remote-arc★ 5same name
    7. yaohuangguan/remote-arc★ 5same name
    8. CsHeng/agent-skills★ 3same name
    9. otaviobarros/agent-engineering★ 3same name
    10. EJRyan89/coding-agent-skills★ 2same name

    6 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use review-change, review-code and 1 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • thlaureSkill

      review-change

      Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Signalist change follows project conventions.

      Also in 3 projects that use this

    • NVIDIASkill

      review-code

      Review a code repository for concrete issues in correctness, robustness, security, maintainability, tests, and integration. Use for repository-wide or focused code review where practical engineering judgment and strict scope control matter.

      Also in 3 projects that use this

    • DockerSkill

      review-pr

      Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.

      Also in 3 projects that use this

  • In this repository16 other files it gives its agents.

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.