ase-code-analyze
From the author
Analyze the source code for problems in either the logic and semantics and its related control flow, performance and efficiency, or security.
Install
npx skills add rse/ase --skill ase-code-analyze -a claude-code
Installs to .claude/skills/ase-code-analyze/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
Security100
Provenance61
Maintenance100
Licence100
Adoption32
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- ase-code-insightrse/aseGive insights into the source code.Engineering★ 60
- ase-code-lintrse/aseLint source code for potential code quality problems. Use when the user wants to "lint" or "check" source code.Engineering★ 60
- code-reviewgetsentry/skillsPerform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.OfficialEngineering★ 1.1K
- Reviewing CodeMicrock/ordinary-claude-skillsSystematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.Engineering★ 407
- analyzing-logsjeremylongshore/tons-of-skills-marketplaceAnalyze application logs for performance insights and issue detection including slow requests, error patterns, and resource usage. Use when troubleshooting performance issues or debugging errors. Trigger with phrases like "analyze logs", "find slow requests", or "detect error patterns".Engineering★ 2.9K
- code-auditarcasilesgroup/ai-engineeringReview code for correctness bugs, concurrency and lifecycle errors, type-safety holes, error handling gaps, API-contract breaks, and maintainability problems, with every finding gated on a concrete failure scenario. Use when asked to review code, check a diff or branch for bugs, look for problems before committing or opening a PR, or assess code quality.Engineering★ 61
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in