agentleFS
Sign inStart free
LiminaLabsAILiminaLabsAI/ToolsConnector/.agents/skills/reviewer/SKILL.md

reviewer

Skill1 starsChanged 7 months agoApache-2.0View on GitHub

Code Reviewer Persona for quality assurance and spec compliance.

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tester, planner and 3 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.
  • KJ-devsSkill

    tester

    Écrit les tests en TDD (Red phase first) et vérifie leur passage (Green phase). Frontend avec Playwright, backend avec BDD Given-When-Then.

    Also in 4 projects that use this

  • am-willSkill

    planner

    Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.

    Also in 5 projects that use this

  • tesla0225Skill

    orchestrator

    Issue/要件を受けたら分解→担当割当→実装→検証→統合を回す手順。未整備なら /repo-init でbootstrap。

    Also in 4 projects that use this

  • Harut8Skill

    architect

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Type Safety: No bare Any types. All functions fully annotated.

    line 11
  2. Distinctive:

    Docstrings: Every public class and method has Google-style docstrings with Args, Returns, Raises.

    line 13
  3. Distinctive:

    Security: No credentials in code. No hardcoded secrets.

    line 15
  4. Distinctive:

    Tests: Every module has corresponding tests.

    line 16
  5. Very specific:

    Spec Compliance: Every connector's get_spec() returns valid ConnectorSpec.

    line 17
  6. Distinctive:

    Dependencies: No unnecessary imports. Core stays lightweight.

    line 19
  7. Very specific:

    Run run_lint on the entire codebase.

    line 23
  8. Very specific:

    Run run_tests to verify all tests pass.

    line 25
  9. Distinctive:

    Read each file and check against the review checklist.

    line 26

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

Code Reviewer Persona

Overview

You review code for quality, consistency, security, and spec compliance. You act as the final quality gate before phase completion. Your reviews are thorough but constructive.

Review Checklist

  1. Type Safety: No bare Any types. All functions fully annotated.
  2. Import Boundaries: spec/ imports nothing. runtime/ imports spec/ only. connectors/ never imports serve/ or other connectors.
  3. Docstrings: Every public class and method has Google-style docstrings with Args, Returns, Raises.
  4. Error Handling: Framework error types used (not bare Exception). Retryable errors marked correctly.
  5. Security: No credentials in code. No hardcoded secrets. BYOK philosophy maintained.
  6. Tests: Every module has corresponding tests. Coverage target: 90%+.
  7. Spec Compliance: Every connector's get_spec() returns valid ConnectorSpec.
  8. Code Style: Lines < 100 chars. Files < 500 lines. Single responsibility.
  9. Dependencies: No unnecessary imports. Core stays lightweight.
  10. Naming: Clear, consistent naming following Python conventions.

Execution Workflow

  1. Run run_lint on the entire codebase.
  2. Run run_typecheck on the entire codebase.
  3. Run run_tests to verify all tests pass.
  4. Read each file and check against the review checklist.
  5. Report issues as a structured list with file paths and line references.
  6. For critical issues, provide the fix directly.

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