Code Analyzer
Review code structure, complexity, and security patterns under a hard read-only guarantee — the editing tools are removed for the turn, so findings can be produced against an untrusted or production checkout without any risk of a write. Use when auditing an unfamiliar codebase, scoping a refactor, or reviewing a branch that has to stay unmodified.
Install
/plugin marketplace add tomada1114/tomada-claude-pluginsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add tomada1114/tomada-claude-plugins --skill code-analyzergit clone --depth 1 https://github.com/tomada1114/tomada-claude-plugins.git /tmp/tomada-claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/tomada-claude-plugins/tomada-kit/skills/creating-agent-skills/examples/code-analyzer ~/.claude/skills/code-analyzerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Code Analyzer Demonstrates the two tool fields, which do opposite things and are constantly confused. ## The two fields - `allowed-tools: Read, Grep, Glob` — **pre-approval**. These run without a permission prompt for the rest of the turn. It grants; it does not restrict. - `disallowed-tools: Write, Edit, NotebookEdit` — **removal**. These leave Claude's pool while the skill is active. This is the line that makes the skill read-only. Listing only `allowed-tools` would leave `Write` and `Edit` fully available, merely prompting for permission as usual. Pick the fields by intent: pre-approve the tools the task hammers, remove the tools whose absence is the guarantee you are selling. Both fields clear when the user sends the next message. For a restriction that outlives the turn, use deny rules in permission settings. ## Procedure Glob to scope, Grep to locate, Read to confirm. Report each finding as `<file>:<line>` plus the specific change that resolves it. Where a fix is non-obvious, write the replacement inline in the report — the whole value here is that the user applies it, not you.
Details
- Skill name
code-analyzer- Repository
- tomada1114/tomada-claude-plugins
- Path
tomada-kit/skills/creating-agent-skills/examples/code-analyzer/SKILL.md- Repo updated
- 12 November 2026
FAQ
What does the Code Analyzer skill do?
Review code structure, complexity, and security patterns under a hard read-only guarantee — the editing tools are removed for the turn, so findings can be produced against an untrusted or production checkout without any risk of a write. Use when auditing an unfamiliar codebase, scoping a refactor, or reviewing a branch that has to stay unmodified.
How do I install the Code Analyzer skill?
Claude Code plugin: /plugin marketplace add tomada1114/tomada-claude-plugins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Code Analyzer popular?
It lives in tomada1114/tomada-claude-plugins, which has 5 GitHub stars and 0 forks.
Related skills
Auditing Prompt Docs
5tomada1114/tomada-claude-plugins
Audit and fix prompt-bearing documents — SKILL.md, CLAUDE.md, AGENTS.md, agent and command definitions, reference files, whole repositories — against Anthropic's published prompting guidance for current Claude models, proposing edits for approval before writing anything. Also answers how to prompt a specific model: holds the per- model guidance for Claude Fable 5.2, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5 alongside the cross-model practices. Use when reviewing or slimming an instruction file, when instructions are ignored or fire too often, when migrating a prompt to a newer m
Auditing Repositories
5tomada1114/tomada-claude-plugins
Audit the repository you are in, often a template or an app cut from one, for technical debt and room to improve in four areas: architecture and design patterns; tests; file structure and code quality; and tooling, CI, dependencies and the agent harness. Design a safe, test-first fix for every evidenced finding, and file the findings as GitHub issues that follow the repository's own issue conventions (triaging-issues, issue forms, past issues). A finding inherited from the template is also filed in the template repository. Cheap read-only sub-agents collect the evidence and high-effort analyst
Authoring Goal Prompts
5tomada1114/tomada-claude-plugins
Author a self-contained prompt for Claude Code's /goal command, run unattended in a separate session — a lead-to-staff handoff where this session researches, designs, and decides with full context, and a fresh executor session (Opus 5.5 or Fable 5.2, with none of that context) implements. Drafts a goal with measurable done-criteria, transcript-verifiable checks, scope + anti-cheat constraints, and stop rules; packages design intent, code examples, research findings, checklists, and pre-answered decisions as support files in a per-goal state directory whenever the executor would otherwise re-de
Code Friction
5Magnus-Gille/claude-skills
Capture a small, opt-in set of concrete code-changeability observations during a coding task and hand them to Close without affecting readiness.
Bun Workspaces
9jarle/bun-skills
Develop complex monorepos with multiple independent packages
Codex CLI Config
5tomada1114/tomada-claude-plugins
Reference for OpenAI Codex CLI configuration, permissions, sandboxing, and autonomy — sandbox_mode and permission profiles, approval_policy, Rules (.rules / prefix_rule), config.toml precedence and trust, AGENTS.md discovery, task design (Mini Codex, Done When, Plan mode), Skills/Plugins/subagents/MCP, and running Codex unattended in CI or Automations. Use when configuring Codex CLI, loosening or tightening its sandbox, diagnosing why a config.toml, AGENTS.md, or Rules file is not taking effect, or writing task prompts and AGENTS.md content Codex will act on well. Also applies when Codex CLI i
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.