roomkit-live/roomkit/examples/skills/code-review/SKILL.md
code-review
Review Python code for bugs, security issues, and style problems
- Source repository stars
- 30
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-07-28
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
When reviewing Python code, follow this checklist:
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/roomkit-live/roomkit --skill "examples/skills/code-review"Inspect the Agent Skill "code-review" from https://github.com/roomkit-live/roomkit/blob/74138265d6e8d9417a14488f9cac0e11e6f493fc/examples/skills/code-review/SKILL.md at commit 74138265d6e8d9417a14488f9cac0e11e6f493fc. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 59/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 30 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | catalog record | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- roomkit-live/roomkit
- Skill path
- examples/skills/code-review/SKILL.md
- Commit
- 74138265d6e8d9417a14488f9cac0e11e6f493fc
- License
- MIT
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
Code Review Skill
When reviewing Python code, follow this checklist:
- Security -- check for SQL injection, command injection, XSS, and unsafe deserialization.
- Logic errors -- verify edge cases, off-by-one errors, and unhandled None values.
- Performance -- flag O(n^2) patterns, unnecessary copies, and blocking calls in async code.
- Style -- enforce project conventions from the style-guide reference.
Always start by reading the style-guide reference to understand the project's conventions before commenting on style issues. Cite specific line numbers when reporting problems.
Alternatives
Compare before choosing
event4u-app/agent-config
code-review
Use when the user says "review this", "check my code", or wants feedback on changes. Reviews for correctness, quality, security, and coding standards.
wshobson/agents
python-design-patterns
Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use this skill when designing a new service or component from scratch and choosing how to layer responsibilities, when refactoring a God class or monolithic function that has grown too large, when deciding whether to add a new abstraction or live with duplication, when evaluating a pull request for structural issues like tight coupling or leaking internal types, when choosing b
wshobson/agents
code-review-excellence
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
openai/skills
security-best-practices
Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.