Library · Team · CrewAI · coding-review
Coding Review — CrewAI
Review a diff or file for bugs, risky paths, and missing tests — without auto-committing or running destructive commands. (CrewAI multi-agent Python sketch for one job.)
Id: crewai/coding-review · Slug: coding-review · Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.
What is this
AI Team for CrewAI. Review a diff or file for bugs, risky paths, and missing tests — without auto-committing or running destructive commands. (CrewAI multi-agent Python sketch for one job.)
How this runtime fits
This CrewAI sketch is a AI Team implementation typed as AI Team in the catalog. Where roles coordinate, it is fair to call it an agent team or multi-agent system — not a swarm.
Parent AI Team: coding-review · What is an AI Team?
What it does
Review a diff or file for bugs, risky paths, and missing tests — without auto-committing or running destructive commands. (CrewAI multi-agent Python sketch for one job.)
Who for
Builders working on Engineering jobs who can run CrewAI themselves.
Works with
Need to run
- You will run this locally or on infra you control.
- No production credentials in prompts or committed files.
- Python 3.10+
- CrewAI in a venv
- Local or keyed LLM endpoint with budget awareness
How to use
- Create a venv; install CrewAI (pin versions yourself).
- Configure a local OpenAI-compatible base URL when possible.
- Save crew_coding_review.py and run: python crew_coding_review.py
- Replace PASTE_EXAMPLE_IN with your real input.
- Read Pass/Fail gate output before trusting the draft.
Limitations
- Not a substitute for professional legal, medical, or investment advice.
- Outputs can be wrong; human review required before publish or spend.
- Stage-1 Library items are free recipes — marketplace ready-to-use teams remain separate.
- Do not attach billing cloud LLM nodes without a human budget check.
Test status
Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.
Files
crew_coding_review.py— CrewAI agents + tasksrequirements-hint.txt— Suggested packages (pin yourself)
Full prompt / config / code
# crew_coding_review.py — Coding Review (CrewAI)
# Safety: local/OpenAI-compatible endpoint preferred. No keys in source.
# pip install crewai (pin versions yourself)
from crewai import Agent, Task, Crew, Process
SYSTEM = """You are a code review specialist. Goal: find bugs and risks in the pasted diff/file.
RULES:
- Do not rewrite the whole codebase. Comment on the provided snippet only.
- Flag: correctness, security, missing tests, irreversible ops, secrets.
- Never suggest committing secrets, force-push, or rm -rf style cleanup.
- Propose patches as unified-diff style snippets when useful.
- Stop with a severity-ordered list. Human decides merges.
OUTPUT:
1) Summary (2-4 sentences)
2) Issues table: severity | location | issue | suggested fix
3) Tests to add
4) What looks fine"""
GOAL = "Review a diff or file for bugs, risky paths, and missing tests \u2014 without auto-committing or running destructive commands."
lead = Agent(
role="Coding Review lead",
goal=GOAL,
backstory="Local BotShelf operator. One job, then stop. No spend. No destructive tools.",
allow_delegation=False,
verbose=False,
)
reviewer = Agent(
role="Quality gate",
goal="Check the lead output against the required sections; list gaps only.",
backstory="Pedantic reviewer. Does not invent facts.",
allow_delegation=False,
verbose=False,
)
produce = Task(
description=(
"Follow SYSTEM strictly.\n\nSYSTEM:\n" + SYSTEM +
"\n\nUSER INPUT:\n{user_input}"
),
expected_output="Complete Coding Review structured result.",
agent=lead,
)
gate = Task(
description=(
"Verify the previous result has all required sections. "
"Return Pass/Fail + missing sections. Do not rewrite creatively."
),
expected_output="Pass/Fail and gap list.",
agent=reviewer,
)
crew = Crew(
agents=[lead, reviewer],
tasks=[produce, gate],
process=Process.sequential,
)
def run(user_input: str) -> str:
return str(crew.kickoff(inputs={"user_input": user_input}))
if __name__ == "__main__":
print(run("PASTE_EXAMPLE_IN"))
Example in
Review this Python snippet:
```
def pay(user, amount):
charge(user.card, amount)
send_receipt(user.email)
```
Context: internal tool, no retries yet.Example out
Summary: Charge-then-receipt with no idempotency or failure handling. Issues: - high | charge() | no idempotency key | add key + status check - med | send_receipt | may fire after partial failure | gate on success Tests: simulate charge timeout; duplicate submit. Looks fine: clear happy-path shape.
Model / runtime notes
Two-agent crew (produce + gate). Keep tools disabled unless you add read-only tools on purpose.
Canonical Team
Parent: coding-review
· implementation_id: crewai/coding-review
GitHub source
teams/coding-review/crewai · commit eb87e8e049fdf9908e438305ff827c7b617505b5
· license: free-use-at-own-risk
Structural check: PASS · env: structural (structural only — does not set Verified)
Related Library items
Related marketplace Team pages
Soft thematic links only — not identity merges. Marketplace Teams ≠ Library AI Team records.
- Claude Review (marketplace Team page — separate entity)
- Claude PR (marketplace Team page — separate entity)