agentleFS
christofferbergjchristofferbergj/agent-skills/skills/reviews/council/SKILL.md

council

Skill1 starsChanged 26 days agoMITView on GitHub

Trigger this if the user says 'council'.

167 other projects use a version of this, 9 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-payment-x402, motion-advanced 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.
  • TironFoxSkill

    agent-payment-x402

    Add x402 payment execution to AI agents — per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents need to pay for APIs, services, or other agents.

    Also in 5 projects that use this

  • renepfSkill

    motion-advanced

    Advanced motion patterns for React / Next.js — drag & drop, gestures, text animations, SVG path drawing, custom hooks, imperative sequences (useAnimate), loaders, and the full API decision tree. Requires motion-foundations.

    Also in 4 projects that use this

  • RojiosSkill

    defi-amm-security

    Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, CEI ordering, donation or inflation attacks, oracle manipulation, slippage, admin controls, and integer math.

    Also in 6 projects that use this

  • scottwaterSkill

    modernize

    Rebase an aging PR onto its current base and decide whether it should be modernized, reworked, or closed. Use when asked to rebase, update, or modernize an old PR.

    Also in 7 projects that use this

  • RojiosSkill

    dart-flutter-patterns

    Production-ready Dart and Flutter patterns covering null safety, immutable state, async composition, widget architecture, popular state management frameworks (BLoC, Riverpod, Provider), GoRouter navigation, Dio networking, Freezed code generation, and clean architecture.

    Also in 5 projects that use this

  • scottwaterSkill

    leaving-pr-comments

    Format comments an agent posts on GitHub on the user's behalf. Use whenever leaving a PR comment, review comment, or reply.

    Also in 6 projects that use this

  • +1 more from scottwater
  • +1 more from Rojios

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 150 edited versions we read keep these.

  • 8

    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:

    Before an audit, address outstanding PR comments, fix known issues, and run relevant checks.

    line 8
  2. Distinctive:

    Do not wait idle. When a result arrives, check its findings against the code at once and decide what to fix while the other delegates run.

    line 45
  3. Distinctive:

    If the work ends in a pull request, put the results in the PR description.

    line 55
  4. Distinctive:

    Put this section right after the description's Evidence section:

    line 56
  5. Very specific:

    If a delegate gives no score, write no score.

    line 69
  6. Distinctive:

    If the PR is open, edit the description.

    line 70
  7. Distinctive:

    If there is no PR, put the same results in the final reply only.

    line 71
  8. Distinctive:

    If you agree with their recommendations, make the changes and request a fresh review after.

    line 73
  9. Distinctive:

    Do not let repeated reviews result in scope creep.

    line 77

“Common” is measured: kept by at least 6 in 10 of the 150 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

Council

Before an audit, address outstanding PR comments, fix known issues, and run relevant checks. Give council the updated implementation; do not defer known fixes until reviews return. If the user wants to discard the implementation and explore new ideas, skip fixes to code being replaced.

Bring in one delegate per model maker to help with the user's request, usually for review or feedback. Use one strong model from each maker the session can reach, at high reasoning effort. If the user's instructions name council members, use those. Otherwise pick each maker's flagship in daily use, for example Claude Opus and GPT Sol, which is not always its newest model.

In T3 Code, call orchestrator_capabilities without search, since a search filters every provider's list. A named member runs on the provider that lists it. Otherwise take every provider with canRunChildTask: true, and make its first listed model its member: the top of its model list in T3 Code, which the user can reorder there, decides over model names. Seat one member per maker, the company a model's id names, such as claude- for Anthropic or gpt- for OpenAI. Instances of one driver count once, chosen as /swarm's T3 route chooses; when two providers' members share a maker, keep the maker's own harness, such as Codex for OpenAI. Start every member in parallel through /swarm's T3 route. Elsewhere, seat /swarm's panel: the session's model and the counterpart.

On every route, pass each member's model and high effort. A Codex member takes only its serviceTier from /swarm's review-full target in Claude Code, or its judgment-and-prose target in Codex. If fewer than two makers are reachable, or a member is unavailable, report it instead of substituting. A member is unavailable when it still fails after its route's one retry, or when its Codex target is fallback; take none of /swarm's other routes or models for it.

Give each delegate the request and relevant context, and for a code review the proof and report lines of /review-loop's reviewer brief. For review or feedback, keep their work read-only. Collect their responses, verify each finding as /review-loop's Verify and merge step does, and summarize the useful findings, disagreements, and recommended next steps.

Do not wait idle. When a result arrives, check its findings against the code at once and decide what to fix while the other delegates run. Do not edit files while a delegate still reviews the same checkout. If the user's instructions mark a delegate as non-blocking, do not wait for it; treat a late result as feedback and do not record its score.

For a code review, ask each delegate for a score out of 10. Count each full review pass as one round. A fresh review after fixes starts a new round.

If the work ends in a pull request, put the results in the PR description. Put this section right after the description's Evidence section:

## Council review

Rounds: 2

| Delegate    | Round 1 | Round 2 |
| ----------- | ------- | ------- |
| Claude Opus | 7/10    | 9/10    |
| GPT Sol     | 8/10    | 10/10   |

If a delegate gives no score, write no score. Do not invent one. If the PR is open, edit the description. Do not post a comment for this. If there is no PR, put the same results in the final reply only.

If you agree with their recommendations, make the changes and request a fresh review after. Continue this process until all delegates are satisfied with the outcome, stopping sooner where /review-loop's step 5 stops.

Do not let repeated reviews result in scope creep. It is your job to fight to keep scope limited.

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.