sc-analyze
Skill19 starsChanged 8 months agoMITView on GitHub
Comprehensive code analysis, quality assessment, and issue diagnosis. Use when analyzing code quality, security vulnerabilities, performance bottlenecks, architecture reviews, or troubleshooting bugs and build failures.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kreighmitchell/SuperClaudeword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- kreighmitchell/SuperClaude★ 4100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-data-engineerSkill
- agent-fullstack-developerSkill
- agent-kubernetes-specialistSkill
- agent-ml-engineerSkill
- agent-performance-engineerSkill
- agent-react-specialistSkill
- agent-security-engineerSkill
- agent-technical-writerSkill
- ask-multiSkill
- askSkill
- learned-skills-indexSkill
- sc-brainstormSkill
- sc-buildSkill
- sc-cicd-setupSkill
- sc-code-reviewSkill
- sc-designSkill
- sc-documentSkill
- sc-e2eSkill
- sc-estimateSkill
- sc-evaluateSkill
- sc-explainSkill
- sc-gitSkill
- sc-implementSkill
- sc-improveSkill
- sc-log-fixSkill
- sc-mcpSkill
- sc-pr-checkSkill
- sc-pr-fixSkill
- sc-principlesSkill
- sc-pushSkill
- sc-readmeSkill
- sc-researchSkill
- sc-tddSkill
- sc-testSkill
- sc-workflowSkill
- sc-worktreeSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Recommend: - Create actionable recommendations
- Very specific: line 66
When --troubleshoot is enabled:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Analysis & Troubleshooting Skill
Multi-domain code analysis with issue diagnosis and resolution capabilities.
Quick Start
# Quality analysis
/sc:analyze [target] --focus quality|security|performance|architecture
# Troubleshooting mode
/sc:analyze [issue] --troubleshoot --focus bug|build|performance|deployment
# With auto-fix
/sc:analyze "TypeScript errors" --troubleshoot --focus build --fixBehavioral Flow
- Discover - Categorize source files, detect languages
- Scan - Apply domain-specific analysis techniques
- Evaluate - Generate prioritized findings with severity
- Recommend - Create actionable recommendations
- Report - Present comprehensive analysis with metrics
Flags
| Flag | Type | Default | Description |
--focus | string | quality | quality, security, performance, architecture, bug, build, deployment |
--troubleshoot | bool | false | Enable issue diagnosis mode |
--trace | bool | false | Detailed trace analysis for debugging |
--fix | bool | false | Auto-apply safe fixes |
--depth | string | standard | quick, standard, deep |
--format | string | text | text, json, report |
Analysis Domains
Quality Analysis
- Code smells and maintainability issues
- Pattern violations and anti-patterns
- Technical debt assessment
Security Analysis
- Vulnerability scanning
- Compliance validation
- Authentication/authorization review
Performance Analysis
- Bottleneck identification
- Resource utilization patterns
- Optimization opportunities
Architecture Analysis
- Component coupling assessment
- Dependency analysis
- Design pattern evaluation
Troubleshooting Mode
When --troubleshoot is enabled:
| Focus | Behavior |
| bug | Error analysis, stack traces, code inspection |
| build | Build logs, dependencies, config validation |
| performance | Metrics analysis, bottleneck identification |
| deployment | Environment analysis, service validation |
Examples
Security Deep Dive
/sc:analyze src/auth --focus security --depth deepBuild Failure Fix
/sc:analyze "compilation errors" --troubleshoot --focus build --fixPerformance Diagnosis
/sc:analyze "slow API response" --troubleshoot --focus performance --traceMCP Integration
PAL MCP (Always Use)
| Tool | When to Use | Purpose |
mcp__pal__thinkdeep | Complex issues | Multi-stage investigation with hypothesis testing |
mcp__pal__debug | Bug troubleshooting | Systematic root cause analysis |
mcp__pal__codereview | Quality analysis | Comprehensive code quality, security, performance review |
mcp__pal__consensus | Critical findings | Multi-model validation of security/architecture issues |
mcp__pal__challenge | Uncertain findings | Force critical thinking on ambiguous issues |
mcp__pal__apilookup | Dependency issues | Get current API docs for version conflicts |
PAL Usage Patterns
# Deep investigation (--depth deep)
mcp__pal__thinkdeep(
step="Investigating performance bottleneck in API layer",
hypothesis="Database queries lack proper indexing",
confidence="medium",
relevant_files=["/src/api/users.py"]
)
# Security analysis (--focus security)
mcp__pal__codereview(
review_type="security",
findings="Authentication, authorization, injection vectors",
issues_found=[{"severity": "high", "description": "SQL injection risk"}]
)
# Critical finding validation
mcp__pal__consensus(
models=[
{"model": "gpt-5.2", "stance": "for"},
{"model": "gemini-3-pro", "stance": "against"}
],
step="Evaluate: Is this a critical security vulnerability?"
)Rube MCP (When Needed)
| Tool | When to Use | Purpose |
mcp__rube__RUBE_SEARCH_TOOLS | External analysis | Find security scanners, linters |
mcp__rube__RUBE_MULTI_EXECUTE_TOOL | Issue tracking | Create tickets for findings |
mcp__rube__RUBE_REMOTE_WORKBENCH | Bulk analysis | Process large codebases |
Rube Usage Patterns
# Find and create Jira tickets for findings
mcp__rube__RUBE_SEARCH_TOOLS(queries=[
{"use_case": "create jira issue", "known_fields": "project:SECURITY"}
])
# Notify team of critical findings
mcp__rube__RUBE_MULTI_EXECUTE_TOOL(tools=[
{"tool_slug": "SLACK_SEND_MESSAGE", "arguments": {"channel": "#security", "text": "Critical finding..."}}
])Flags (Extended)
| Flag | Type | Default | Description |
--pal-deep | bool | false | Use PAL thinkdeep for multi-stage analysis |
--pal-review | bool | false | Use PAL codereview for comprehensive review |
--consensus | bool | false | Use PAL consensus for critical findings |
--notify | string | - | Notify via Rube (slack, jira, email) |
--create-tickets | bool | false | Create tickets for findings via Rube |
Tool Coordination
- Glob - File discovery and structure analysis
- Grep - Pattern analysis and code search
- Read - Source inspection and config analysis
- Bash - External tool execution
- Write - Report generation
- PAL MCP - Multi-model analysis, debugging, code review
- Rube MCP - External notifications, ticket creation
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

