agentleFS
dativo-iodativo-io/talon/.claude/skills/architecture-review/SKILL.md

architecture-review

Skill18 starsChanged 25 days agoApache-2.0View on GitHub

Review a proposed or existing Talon change against current architecture and product boundaries without implementing it.

85 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-stories, story-done and 10 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.
  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 11 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 11 projects that use this

  • +10 more from lilangMax

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 77 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read current #265 and the relevant active issue(s).

    line 9
  2. Very specific:

    Check for duplicated policy/state/projection paths and accidental scope expansion.

    line 19
  3. Distinctive:

    Do not create issues, comments, branches, commits, or PRs unless explicitly authorized.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 77 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Review $ARGUMENTS without editing code.

  1. Read current #265 and the relevant active issue(s).
  2. Inspect the existing implementation and tests; do not review from issue text alone.
  3. Identify:
    • canonical domain owner;
    • adapters and trust boundaries;
    • persisted/wire/config contracts;
    • source-of-truth relationships;
    • failure/retry/recovery semantics;
    • enforcement boundary and bypasses;
    • evidence/projection consequences.
  4. Check for duplicated policy/state/projection paths and accidental scope expansion.
  5. Separate:
    • shipped behavior;
    • active target;
    • parked/future capability.
  6. Evaluate migration/rollback and compatibility consequences.
  7. Define the minimum test pyramid needed to prove the design, including negative proof and failure injection where relevant.
  8. Recommend the smallest architecture that satisfies the active contract.

Do not create issues, comments, branches, commits, or PRs unless explicitly authorized.

Return findings ordered by correctness/security risk first, then complexity/maintainability, then optional improvements.

Download now (ZIP)

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.