panel review

Engineering Community

Skill notes

This review runs as a panel of specialists. Do NOT perform their audits yourself — each auditor applies rules that live only in its own definition, so an inline imitation misses them.

Launch BOTH specialists over the target (Task dispatches): - subagent_type: review-panel:naming-auditor — prompt it with the target path and ask for its full naming/codename audit report. - subagent_type: review-panel:todo-auditor — prompt it with the target path and ask for its full leftover-marker audit report. 2. Wait for both reports. 3. Merge: report every defect either auditor found, keeping each auditor's severity. Add any defect you observed yourself while merging, at your own severity.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@trailofbits · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Panel Review

This review runs as a panel of specialists. Do NOT perform their audits yourself — each
auditor applies rules that live only in its own definition, so an inline imitation
misses them.

1. Launch BOTH specialists over the target (Task dispatches):
   - `subagent_type: review-panel:naming-auditor` — prompt it with the target path and
     ask for its full naming/codename audit report.
   - `subagent_type: review-panel:todo-auditor` — prompt it with the target path and
     ask for its full leftover-marker audit report.
2. Wait for both reports.
3. Merge: report every defect either auditor found, keeping each auditor's severity.
   Add any defect you observed yourself while merging, at your own severity.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.