AndrewDongminYoo
UserClaude Code plugin marketplace. guard-hooks: five defensive hooks that block dangerous shell commands and secrets access, catch the two zsh quoting mistakes that fail silently, and warn on lockfile drift and shellcheck findings.
Categories
Indexed Skills (12)
config-gc
Garbage collection for the active Claude config root — scans skills, memory, hooks, permissions, MCP servers, and caches for redundant, stale, or orphaned items, then walks the user through confirm-each-deletion cleanup. Use on "clean up my config", "config GC", "too many skills", "my .claude is bloated", or a periodic review.
context-budget
Audits Claude Code context window consumption across agents, skills, MCP servers, and rules. Identifies bloat, redundant components, and produces prioritized token-savings recommendations.
handoff
Use when a session's context is getting long or degrading and you need a detailed, self-contained summary to manually paste into a fresh session (or hand to another machine/tool/teammate). For a short durable fact instead, write it to the persistent memory directory (auto-loaded via MEMORY.md).
session-export
Export a Claude Code session as Markdown, HTML, or JSON. Use when the user wants to save, archive, share, or re-read a transcript. For a continuation summary, use /handoff instead.
wayfinder
Chart an effort too big for one session as a map of decision tickets under docs/plans/, then resolve one ticket per session until the way to the destination is clear.
ci-babysit
Use after pushing a branch or opening a PR when CI needs monitoring or authorized make-green work. Keeps watch-only requests read-only, requires explicit current-request or approved-plan authority before reruns or local repairs, and stops honestly when a human or logic change is needed. Works in any ecosystem.
cspell-triage
Use when cspell reports unknown words or forbidden words in a repository, when adding entries to a cspell dictionary, or when a cspell config needs setting up, consolidating, or auditing.
fix-osv-vulnerabilities
Use when osv-scanner or trunk check reports dependency vulnerabilities (GHSA-*) in a pnpm/npm/yarn project and you need to triage and fix them.
markdownlint-triage
Use when summarizing Markdownlint logs, selecting useful Markdown rules, or fixing an existing Markdownlint backlog with file-scoped parallel work.
semantic-commit
Use when staged/unstaged changes mix multiple unrelated concerns and need splitting into clean conventional commits, or when asked for "semantic commits", "logical commits", or "커밋 분리". Works in any language or ecosystem.
setup-trunk
Use when integrating trunk.io into a repository for the first time, or when configuring trunk linters, git hooks, and pre-commit/push validation in an existing codebase with legacy lint violations.
log-it
Use when the user asks to record what a session discovered or learned ("기록해줘", "로그 남겨줘", "log this", "/log-it"), when a session ends after non-obvious findings or trial-and-error, or before /clear would lose them.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.