Installs into .claude/skills of the current project.
Are you the author of Tf Review?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/marblo-app-tf-review)
---
name: tf-review
description: Review REVIEW-status tasks as PM, check code quality, then approve or reject.
disable-model-invocation: true
allowed-tools: Bash, Read, Glob, Grep
---
# Marblo PM Review
> Review the REVIEW tasks agents submitted.
> Check code quality and approve (DONE) or reject (revert to TODO).
---
## β Required rule: Marblo MCP only
> **Never use the Claude Code built-in tools (TaskCreate, TaskList, TaskUpdate, TaskGet).**
> Task lookup/status-change MUST use the **Marblo MCP tools**:
> `get_all_tasks`, `update_task_status`, `add_activity`, `get_task_activities`
---
## Step 1: Fetch tasks awaiting review
Filter `get_all_tasks` to only REVIEW status.
```
π Awaiting review: {n}
βββββββββββββ
1. TASK-002: User API (backend)
Submitted: 30 min ago | Owner: backend-agent
2. TASK-004: URL input screen (frontend)
Submitted: 15 min ago | Owner: frontend-agent
```
---
## Step 2: Review each task
For each task, check the following:
### 2-1. Check the activity log
Use `get_task_activities` to understand what the agent did.
### 2-2. Check the code
Read and review the files listed in the task's scope field.
### 2-3. Review checklist
```
β‘ Feature completeness: are all requirements from the task description implemented?
β‘ Code quality: did it follow the skill file's rules (framework, patterns)?
β‘ Tests included: is there test code and does it pass?
β‘ Error handling: are exceptional cases handled properly?
β‘ Scope compliance: did it avoid modifying files outside scope?
β‘ Security: no vulnerabilities like SQL injection, XSS?
```
### 2-4. Verdict
Show the review result to the user:
```
π TASK-002: User API review result
βββββββββββββββββββββββββ
β Feature completeness: signup, login, profile lookup β OK
β Code quality: FastAPI + Pydantic v2 β OK
β Tests: 5/5 pass β OK
β οΈ Error handling: no password validation
β Scope compliance: OK
Verdict: approve or reject?
```
---
## Step 3: Approve / reject
### Approve
- `update_task_status` β DONE
- If it unblocks any tasks, let the user know:
```
β TASK-002 approved β DONE
π TASK-004, TASK-005 are now workable
```
### Reject
- `update_task_status` β TODO (include a feedback comment)
- Record a concrete change request with `add_activity`:
```
β TASK-002 rejected β TODO
Feedback: "Add password validation (8+ chars, include special char).
Make error messages user-friendly too."
```
---
## After review
After handling all REVIEWs, show the status:
```
π Review complete:
Approved: {n}
Rejected: {n}
Newly available tasks: {list}
Next action: /tf-work or re-run the agents
```