agentleFS
Sign inStart free
MrCipherSmithMrCipherSmith/goodai-base/skills/iago/SKILL.md

iago

Skill0 starsChanged 5 months agoMITView on GitHub

Use when generating or updating a Mermaid diagram for a GitHub pull request review, especially after reviewing a diff and needing to explain control flow, sequence, classes, or entity relationships. Triggered by: iago, /iago, /squawk, generate PR diagram, add Mermaid diagram to PR, or visualize this review.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 9 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prefer gh pr diff <pr> for the reviewed diff.

    line 35
  2. Distinctive:

    Use stable node names and short labels.

    line 45
  3. Distinctive:

    Avoid dumping every changed file into the diagram.

    line 46
  4. Very specific:

    Use gh CLI, not GitHub MCP, for GitHub writes.

    line 63
  5. Distinctive:

    Read existing PR body and issue comments.

    line 67
  6. Very specific:

    If an <!-- iago:begin --> / <!-- iago:end --> block already exists, replace only that block.

    line 68
  7. Distinctive:

    If no block exists, create a new top-level PR comment with the block.

    line 69
  8. Distinctive:

    Do not create duplicate iago comments.

    line 70
  9. Distinctive:

    Do not post automatically to a team PR unless the user asked to publish.

    line 82
  10. Distinctive:

    Do not use GitHub MCP comment tools for this skill.

    line 83
  11. Distinctive:

    If repo instructions ban automated GitHub comments broadly, print the block locally and ask before publishing.

    line 84
  12. Distinctive:

    Keep the diagram explanatory, not decorative.

    line 85

≈ “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.

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

Iago

Generate a concise Mermaid diagram that explains the important logic in a PR diff, then either print an idempotent iago block locally or update the PR comment/body when the user explicitly wants it published.

Iago is for review communication, not for finding new review issues. Run a normal review first when the code has not been inspected.

Inputs

  • Optional diagram type: flow, sequence, class, or entity-relation.
  • Optional PR number or URL. If absent, resolve the current branch PR with gh pr view --json number,url,headRefName,baseRefName.
  • Optional publish mode. If the user did not explicitly ask to post/update GitHub, output the block locally only.

Workflow

  1. Resolve PR context.
    • Prefer gh pr diff <pr> for the reviewed diff.
    • Also read relevant changed files when the diff alone is not enough.
  2. Pick the diagram type.
    • flowchart TD for branching logic, save guards, validation paths, and state transitions.
    • sequenceDiagram for BE to FE contracts, request lifecycles, async calls, and event chains.
    • classDiagram for object/model relationships.
    • erDiagram for database entities.
    • Honor an explicit type from /iago <type> or /squawk <type>.
  3. Generate one small diagram.
    • Show only review-relevant logic.
    • Use stable node names and short labels.
    • Avoid dumping every changed file into the diagram.
  4. Wrap the result in the idempotent block:
<!-- iago:begin -->
```mermaid
flowchart TD
  A["Important change"] --> B["Review-relevant outcome"]
```
<!-- iago:end -->
  1. Validate the Mermaid syntax by inspection. Prefer simpler syntax over clever formatting.
  2. Publish only when requested.

Publishing

Use gh CLI, not GitHub MCP, for GitHub writes.

When publishing:

  1. Read existing PR body and issue comments.
  2. If an <!-- iago:begin --> / <!-- iago:end --> block already exists, replace only that block.
  3. If no block exists, create a new top-level PR comment with the block.
  4. Do not create duplicate iago comments.

Suggested commands:

gh pr view <pr> --json number,url,body,comments
gh pr comment <pr> --body-file <file>
gh api repos/:owner/:repo/issues/comments/<comment_id> --method PATCH --field body=@<file>

Safety

  • Do not post automatically to a team PR unless the user asked to publish.
  • Do not use GitHub MCP comment tools for this skill.
  • If repo instructions ban automated GitHub comments broadly, print the block locally and ask before publishing.
  • Keep the diagram explanatory, not decorative.

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.

Check your setup, free