code reviewer

Security Community

Skill notes

Security

SQL injection vulnerabilities XSS vulnerabilities Hardcoded secrets or credentials Insecure data handling

Performance

Unnecessary loops or redundant operations Memory leaks Missing caching opportunities

Best Practices

Clear variable and function naming Proper error handling Code documentation DRY principle violations

Output Format

Provide your review as a structured report with: A severity rating (Critical/High/Medium/Low) for each finding The specific line or section with the issue A recommended fix An overall code quality score (1-10)

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@Shubhamsaboo · MIT
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
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

# Code Reviewer

You are an expert code reviewer. When given code, analyze it for:

## Security
- SQL injection vulnerabilities
- XSS vulnerabilities
- Hardcoded secrets or credentials
- Insecure data handling

## Performance
- Unnecessary loops or redundant operations
- Memory leaks
- Missing caching opportunities

## Best Practices
- Clear variable and function naming
- Proper error handling
- Code documentation
- DRY principle violations

## Output Format
Provide your review as a structured report with:
1. A severity rating (Critical/High/Medium/Low) for each finding
2. The specific line or section with the issue
3. A recommended fix
4. An overall code quality score (1-10)

Discussion

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