Agent skill for code-review-swarm - invoke with $agent-code-review-swarm
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-code-review-swarm30
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
CI workflow for automated PR review
PR event trigger
100%
100%
Full git history fetch
100%
100%
GH CLI auth via token
0%
100%
PR data JSON fetch
100%
100%
PR diff fetch
0%
100%
Swarm review-init command
0%
100%
PR data passed to swarm
30%
100%
Multiple review agents
100%
100%
Initial status comment
0%
100%
Conditional final review action
80%
100%
Review output posted to PR
100%
100%
Without context: $0.2950 · 1m 20s · 17 turns · 22 in / 4,782 out tokens
With context: $0.4429 · 1m 38s · 20 turns · 310 in / 5,618 out tokens
Security review with severity routing
Security agent command
0%
100%
OWASP/CVE check categories
0%
100%
Suggest fixes flag
0%
100%
Critical issue detection
100%
100%
Request changes on critical
100%
100%
Security label on critical
0%
100%
Comment for non-critical
100%
100%
Severity indicator in template
0%
50%
Template sections present
25%
100%
Auth verification
0%
100%
Changed files retrieval
0%
100%
Without context: $0.3291 · 1m 29s · 18 turns · 22 in / 4,920 out tokens
With context: $0.4313 · 1m 17s · 22 turns · 439 in / 4,136 out tokens
Review system configuration file
Correct config filename
0%
100%
Config version field
40%
100%
Auto-trigger enabled
0%
100%
Required agents
30%
100%
Optional agents
0%
100%
Security threshold blocks
37%
100%
Performance threshold warns
0%
100%
Style threshold suggests
100%
100%
Security rules
0%
100%
Performance rules
10%
100%
Architecture coupling limit
0%
100%
Architecture cohesion minimum
28%
100%
High-risk path triggers
88%
100%
Without context: $1.2835 · 4m 20s · 27 turns · 1,760 in / 9,150 out tokens
With context: $0.4703 · 1m 40s · 24 turns · 28 in / 5,350 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.