Explain
Skill steph-dove/klaussy-agents/src/klaussy/templates/skills/explain
A multi-agent context, rules, and hooks boilerplate generator. With a single command, it scaffolds conventions, namespaced skills, stack-appropriate settings, and interactive guardrails for seven major AI coding environments, matching each agent's native file formats and capability profiles.
npx -y skills add steph-dove/klaussy-agents --skill explainAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when the user wants code, a concept, or the current diff explained in this repo. With no specific target, explains the current branch diff; with a target, traces call chains and data flow end-to-end and explains in plain language.
SKILL.md
2.3 KB, as published. Nobody here has run it
Target
$ARGUMENTS
If $ARGUMENTS is empty, explain the current branch diff using the dump below. Otherwise, treat $ARGUMENTS as the target — a file path, function name, or concept — and explain that.
Current branch diff (used when target is empty)
git diff {{BASE_BRANCH}}...HEAD
Instructions
If the target is empty (no arguments):
- The diff above shows everything changed on this branch. If it's empty, fall back to
git diff(unstaged) andgit diff --cached(staged). - Read the full files involved to understand the surrounding context — do not paraphrase from the diff alone.
- Explain what changed and why, covering:
- The purpose of the changes as a whole
- How the modified components interact
- Any non-obvious behavior or edge cases introduced
If the target is provided:
- Read CLAUDE.md and any matching
.claude/rules/*.mdfor the area the target lives in. - Find the relevant code using Grep and Glob.
- Read the full files involved to understand context.
- Trace the call chain and data flow end-to-end.
- Explain how it works in plain language, covering:
- What it does and why it exists
- Key components and how they interact
- Important design decisions or trade-offs
- Any non-obvious behavior or edge cases
Rules
- Tailor the depth to the question — "what does this function do" needs less than "how does auth work".
- Use concrete examples from the code, not abstract descriptions.
- Cite file:line references when pointing at code.
- If something looks like a bug or smells off, mention it once, then stay focused on explaining.
- Don't suggest changes unless asked.
{{HUMANIZE}}
When NOT to use
- The user wants to change code — use the implement, refactor, debug, or fix skill instead.
- The user wants a code review — use the review skill, which validates findings and structures output.
- The user wants the diff itself, not an explanation of it — they can run
git diffdirectly.