my-skills

Extremely strict maintainability review focused on structural simplification, abstraction quality, and spaghetti-condition growth. Not a general correctness review -- this is a deep code quality audit that pushes for "code judo" moves that delete complexity. Use when asked to "code review", "maintainability review", "code quality audit", "/code-review", or "/review-quality".

Spawns a verifier subagent to audit your work: traces what was done, reviews the diff, runs builds/tests, and delivers a PASS/FAIL verdict. Auto-retries fixes up to 3 rounds. Use when asked to "check work", "verify changes", "self-verify", "/self-verify", "/check", or "/verify".

轻量需求头脑风暴 — 先扫代码库确认前置条件，再用 2-3 轮聚焦讨论锁定范围和方案。Use when user says "brainstorm this feature", "需求讨论", "sdd brainstorm", or wants to explore a feature idea before writing specs. Replaces heavyweight brainstorming workflows that burn tokens.

按规格文档的 Ticket 逐个实现代码，每个 Ticket 独立上下文避免幻觉。内置 todo 进度追踪，支持 LSP 诊断、worktree 隔离、子智能体委派等按需升级。Use when user says "implement ticket", "实现这个任务", "sdd implement", "开始实现", or wants to execute tasks from a spec. Reads .plan/spec.md for task breakdown.

将头脑风暴结论转化为结构化规格文档，包含需求、技术设计、任务拆解和决策记录。Use when user says "write spec", "写规格", "sdd spec", or wants to formalize a brainstormed idea into an implementable specification. Reads .plan/brainstorm.md if available.

Comprehensive quality analysis tool for Claude Skills. Evaluates skills from GitHub URLs, marketplace links, ZIP files, or local directories across five dimensions (structure, security, UX, code quality, integration) using balanced scoring and three output modes (comprehensive report, interactive review, pass/fail certification). Triggers on "analyze skill quality", "review this skill", "evaluate skill", or "skill quality check".

Comprehensive security analysis for Claude Code skills with P0-P3 enhancements. Detects malicious code, obfuscation, YAML injection, typosquatting, time bombs, sandbox escapes, and 40+ attack patterns. Use for analyzing skills before installation or auditing existing skills.

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

Compact the current conversation into a handoff document for another agent to pick up.

Use when drafting, editing, or reviewing prose to eliminate predictable AI writing patterns. Detects filler phrases, formulaic structures, passive constructions, vague declaratives, and rhythm monotony. Supports both English and Chinese text.

整理和优化项目目录结构。当用户请求整理目录、分类文件、清理无用文件或重构文件夹结构时调用此技能。

Use this skill when the user asks to parse or extract text from PDF files locally without cloud dependencies.

Render Mermaid diagrams as SVG or ASCII art using beautiful-mermaid. Use when users need to create flowcharts, sequence diagrams, state diagrams, class diagrams, or ER diagrams. Supports both graphical SVG output and terminal-friendly ASCII/Unicode output.

Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.

当需要搜索符号定义、追踪调用链、分析变更影响、理解陌生模块时，用预索引的代码知识图谱一次调用替代多轮 grep/glob/read_file，工具调用减少 60%+、token 消耗降低 50%+

一个专业的项目规划助手，能够通过多轮对话与你协作，从需求理解到方案设计，最终输出完整的项目计划文档

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".