Comms How
Explain how a subsystem works, its architecture, runtime flow, and where new code belongs. Use for "how does X work", walkthroughs before changing something, and placement or ownership questions like "where should this live" or "which package owns this". Use comms-why for motivation.
Install
npx skills add jpoehnelt/skills --skill comms-howgit clone --depth 1 https://github.com/jpoehnelt/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/comms-how ~/.claude/skills/comms-howPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# How Answer "how does X work?" at the level of a senior engineer onboarding onto a subsystem. Build a working mental model without reading like annotated source. Use `comms-why` for motivation and history. Repo facts: the ownership, layering, and boundary rules in the repo's `AGENTS.md` (or `CLAUDE.md`). ## 1. Assess scope If the question is ambiguous, state your interpretation and proceed. The user can redirect. - **Simple.** One module, one function, or a narrow question. Explore it yourself with the client's file read and search tools (or `rg` and `cat`), then go to step 4. - **Complex.** A subsystem spanning files or services, a cross-cutting feature, or an architecture overview. Go to step 2. When in doubt, take the simple path. ## 2. Explore (complex only) Split the question into 2 to 4 angles, each a distinct slice such as entry points, data model, side effects, or error paths. When delegation is authorized, spawn one read-only exploration subagent per angle, all in a single turn, using a smaller, faster model. (Claude Code: the Agent tool with the Explore type; Codex: its subagent/collaboration tool.) If the client caps concurrent subagents, run the angles in batches within that cap. Without delegation authorization, or when the client cannot spawn subagents, inspect the angles yourself in sequence.
Details
- Skill name
comms-how- Repository
- jpoehnelt/skills
- Path
comms-how/SKILL.md- License
- MIT
- Repo updated
- 12 November 2026
FAQ
What does the Comms How skill do?
Explain how a subsystem works, its architecture, runtime flow, and where new code belongs. Use for "how does X work", walkthroughs before changing something, and placement or ownership questions like "where should this live" or "which package owns this". Use comms-why for motivation.
How do I install the Comms How skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jpoehnelt/skills --skill comms-how. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Comms How popular?
It lives in jpoehnelt/skills, which has 23 GitHub stars and 1 forks.
Related skills
Agents Correct
23jpoehnelt/skills
Find the mistakes agents keep repeating in a repo and make each one impossible, trying architecture first, then types, lint, tests, and docs last. Use when the operator keeps correcting the same mistake, or for /agents-correct.
Agents Create Verification Skill
23jpoehnelt/skills
Generate a project-local verify skill that drives the app like a user through a browser with Playwright, a CLI, or HTTP. Use for /agents-create-verification-skill, "make a verify skill for this repo", or when a project has no scripted way to prove UI, CLI, or service behavior.
Agents Reflect
23jpoehnelt/skills
After a work session, review what went wrong and right and turn each lesson into a concrete edit to an existing skill or AGENTS.md line. Use when the user says "reflect" or /agents-reflect.
Effect
23jpoehnelt/skills
Apply Effect v4 conventions for services, layers, tagged errors, boundary runners, resources, retries, deadlines, HTTP, and tests. Use when writing or reviewing TypeScript that imports effect, adds a service or error class, chooses where to run a program, bounds external I/O, or tests Effect code.
4d V21
9Ganbin/4d-development-skill
Comprehensive 4D v21 development expert with embedded official documentation. Covers ORDA patterns, entity classes, data model classes, queries, classic methods, data types, error handling, forms, events, web server, and REST API. Use when working with 4D files (.4dm), 4D language questions, 4D project structure, entity classes, ORDA queries, database operations, form development, web server configuration, REST API usage, or any 4D-specific syntax issue. Includes full official 4D v21 documentation for on-demand retrieval. Triggers on: .4dm files, 4D code, ORDA, entity selection, dataclass, 4D
Eng Blast Radius
23jpoehnelt/skills
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it is safe because of by running real code. Use when asked for the "blast radius of X" or "what could this break", or when reviewing a small diff you do not trust.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.