code-overview
Produces a human-readable, progressive-disclosure overview of unfamiliar code or a pull request's changes — why it exists (the real problem it solves or…
Examining code for the line that is wrong
What it does
- git installed: !which git 2>/dev/null || echo "not installed" - gh installed: !which gh 2>/dev/null || echo "not installed" - CLAUDE.md: !`find .
Read more
-maxdepth 1 -name "CLAUDE.md" -type f - project-discovery.md: !find . -maxdepth 3 -name "project-discovery.md" -type f - personal config directory: !bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude" - project .han/config.md: !cat .han/config.md 2>/dev/null || echo ""`
Use when you want to understand, get oriented in, make sense of, explain, or
You don’t need to name it. Ask for the job in your own words — your AI loads the skill when the request matches.
What it can touch
No script files in its folder
Its folder holds text, not programs. It changes how your AI works; it does not bring code of its own.
How we know
Listed the 2 files in the skill’s folder on GitHub; none is a script or program.
Lets your AI use some powerful tools without asking, while the skill is in use
While the skill is working, Claude Code will not ask before using these tools.
How we know
SKILL.md line 1: “allowed-tools: Read, Glob, Grep, Agent, Write, Bash(git *), Bash(gh *), Bash(find *), Bash(bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-d…”. Read 2026-10-05, commit abba73a.
SKILL.md, line 1 ↗Runs a command by itself, without asking, as soon as the skill loads
Claude Code runs a command written into the skill the moment the skill is opened, before your AI reads it — no approval is asked unless you have a rule blocking it.
How we know
SKILL.md line 24 (and 5 more in that file): “which git 2>/dev/null || echo "not installed"”. Read 2026-10-05, commit abba73a.
SKILL.md, line 24 ↗No serious risk pattern found
Launch7’s automated check read all 2 text files in this skill and matched none of its serious risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.
How we know
Read 2026-10-05, commit abba73a by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.
Recently maintained
Its repository has had changes recently.
How we know
Last push to testdouble/han: 2026-10-01 (4 days before the scan).
Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Supported. Upload it once in Claude’s settings. Works on every plan, including Free.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end
More from testdouble
All from this publisher →- architectural-analysis
Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns,…
- architectural-decision-record
Create, extract, or convert an ADR (architectural decision record) using the ADR template.
- automated-test-planning
Produce a standalone test plan by analyzing code for test coverage gaps and edge cases.
- code-walkthrough
Walks a person through code changes one step at a time in conversation, starting at the entry point and following the flow that changes, showing a small…
- coding-standard
Creates and updates coding standards, conventions, rules, and guidelines for the current project.
