standard-skill
This skill should be used when the user asks to "analyze code", "review code quality", "check code structure", "find code patterns", or mentions code analysis without making changes.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install rafaelcalleja-claude-market-place-standard-skill
Repository
Skill path: skills/skill-protocol-mastery/examples/standard-skill
This skill should be used when the user asks to "analyze code", "review code quality", "check code structure", "find code patterns", or mentions code analysis without making changes.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: rafaelcalleja.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install standard-skill into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/rafaelcalleja/claude-market-place before adding standard-skill to shared team environments
- Use standard-skill for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: code-analyzer description: This skill should be used when the user asks to "analyze code", "review code quality", "check code structure", "find code patterns", or mentions code analysis without making changes. allowed-tools: Read, Grep, Glob version: 1.0.0 --- # Code Analyzer Analyze code structure and patterns without making modifications. ## Capabilities - Analyze code organization and architecture - Find patterns and anti-patterns - Check naming conventions - Identify potential issues - Review documentation quality ## Workflow ### Step 1: Discover Files Use Glob to find relevant source files: ```bash # Find all TypeScript files *.ts, **/*.ts # Find all Python files *.py, **/*.py ``` ### Step 2: Analyze Structure Use Read to examine file contents and understand: - Module organization - Class hierarchies - Function signatures - Import patterns ### Step 3: Search Patterns Use Grep to find specific patterns: - Error handling patterns - Logging practices - API usage - Configuration access ### Step 4: Report Findings Provide analysis covering: - Code organization - Naming conventions - Potential issues - Improvement suggestions ## Analysis Checklist - [ ] Code structure and organization - [ ] Naming conventions followed - [ ] Comment quality - [ ] Potential bugs or issues - [ ] Performance considerations - [ ] Security concerns ## Additional Resources ### Reference Files For detailed analysis patterns: - **`references/patterns.md`** - Common code patterns to identify - **`references/anti-patterns.md`** - Issues to flag