pi-extension-intake
No SKILL.md available for this skill.
View on GitHubMore from sjunepark/custom-skills
change-explainer
Teach a code or document change set in clear learning order, with embedded snippets, before/after contrasts, and clear implications. Use whenever the user wants help understanding a `git diff`, unstaged changes, a commit, commit range, PR patch, or two versions of a file or document, especially when they want a guided walkthrough that starts with the big picture and then explains why and how the patch works. Prefer this skill when the user wants snippets instead of file or line references, even if they only ask "walk me through this diff" or "help me understand these changes.
19planning-doc-triad
Maintain project planning with three distinct documents: a big-picture roadmap, a near-term TODO list, and one active detailed plan. Use this skill when the user wants to create, clean up, or reset repository planning docs such as a roadmap, TODO file, or active plan, or when those roles are blurred across existing files. Do not use it for generic requests for priorities, next steps, or an implementation plan unless the user is explicitly asking to update or establish planning documents.
11lean-review
Review code for unnecessary structure, speculative design, and low-value complexity without attacking readability. Use whenever the user asks whether code is overengineered, too abstract, too configurable, too future-proof, whether extra DB columns/fields/helpers should exist, whether a change feels heavier than necessary, or wants help simplifying code while keeping readability benefits such as clear names, small object boundaries, or helpful file structure.
1fs-merge
Merge multi-year Korean financial statements (재무제표: BS, PL, 제조원가명세서) from PDFs or spreadsheets into one comparison .xlsx. Use when the user provides two or more Korean FS files and asks to consolidate, compare, 합본, 합치기, combine year-over-year statements, or build a merged workbook.
1