Skip to content
TrustedSkillsbeta
Back to all skills

Code Analyzer

Checked
oimiragieo·vlatest·backend

The Code Analyzer skill swiftly identifies potential bugs, vulnerabilities, and style issues in your code, boosting development efficiency and code quality.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add oimiragieo/agent-studio --skill code-analyzer -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

oimiragieo

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned oimiragieo/agent-studio at 64b580eab2.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
64b580eab2
Manifest
.claude/skills/code-analyzer/SKILL.md
Scanned
10 files, 364 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Code Analyzer skill performs static code analysis and calculates various metrics to identify potential bugs, vulnerabilities, and style issues within your codebase. It leverages a tool called analyzer.mjs which runs automatically from the project root. The goal is to improve development efficiency and overall code quality by highlighting areas needing attention.

When to use it

  • Before refactoring: Analyze code before making significant changes to understand its structure and potential impact.
  • During code review: Identify complex or problematic sections for reviewers to focus on.
  • As part of a CI/CD pipeline: Integrate the analyzer into your automated build process to catch issues early (using project-analyzer/doctor for health checks).
  • To track code quality trends: Monitor metrics over time to identify areas where code is degrading or improving.

Key capabilities

  • Project-wide analysis: Analyzes the entire project codebase.
  • File-specific analysis: Allows analyzing a single file.
  • Complexity calculation: Calculates cyclomatic complexity, lines of code (LOC), maintainability index, and identifies duplicate blocks.
  • Hotspot identification: Pinpoints areas with high complexity for focused review.
  • Trend analysis: Tracks metric trends over time to monitor code quality changes.
  • Integration with other agents: Works well with code-reviewer, refactoring-specialist, and architect AI agent roles.

Example prompts

  • "Analyze the entire project for complexity hotspots."
  • "Can you summarize the analysis of this file?" (followed by providing a filename)
  • "Show me the trends in cyclomatic complexity over the last week."

Tips & gotchas

  • Node.js Requirement: Ensure Node.js version 18 or higher is installed before using the skill.
  • Start Broad, Then Focus: Always run project-wide analysis before drilling down into individual files for best results.
  • Prioritize Churn: When identifying hotspots, prioritize files with both high complexity and frequent changes (high churn).