agentleFS
apinto25apinto25/claude-code-agents-skills/.claude/skills/python-review/SKILL.md

python-review

Skill2 starsChanged 6 months agoNo licenceView on GitHub

Reviews Python code for PeP8 compliance, type hints, docstrings, and common anti-patterns. Use when the user asks to "review", "check quality", or "improve" Python code quality.

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use go-review, typescript-review 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.
  • TheKREATORSSkill

    go-review

    Comprehensive Go code review for idiomatic patterns, concurrency safety, error handling, and security. Invokes the go-reviewer agent.

    Also in 5 projects that use this

  • weiweimhySkill

    typescript-review

    TypeScript code review guidance for type safety, generics, narrowing, public API types, runtime validation alignment, async flow, TSX, and strict tsconfig. Use when reviewing .ts or .tsx files, Node/React/Vue TypeScript, or complex types.

    Also in 4 projects that use this

  • CloudflareSkill

    rust-review

    Rust code review for workerd. Covers CXX FFI safety, unsafe code patterns, JSG resource conventions, error handling, and a review checklist adapted from the C++ review skills. Load this skill when reviewing Rust code in src/rust/.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.