post-implementation-review
No SKILL.md available for this skill.
View on GitHubMore from sjunepark/custom-skills
agents-md-writer
Create, edit, review, and improve AGENTS.md files for repositories used by agentic coding tools with concise, actionable instructions and correct precedence behavior. Use whenever AGENTS.md content is being changed, including updating existing guidance, drafting a new AGENTS.md, migrating legacy instruction files, defining nested overrides in monorepos, or debugging why tools load the wrong guidance.
26source-investigator
Investigate external libraries, frameworks, and unfamiliar repositories by cloning the exact repo into a project-local temp workspace, ignoring that workspace in git, and delegating code reading to focused subagents so the main thread stays clean. Use whenever docs are incomplete, version-specific behavior matters, you need to learn how a codebase works, or exploring lots of source inline would pollute the main context.
24doc-comment-writer
Add or improve doc comments in mentioned source files without filling the code with obvious restatements. Use whenever the user asks to document code, add doc comments, explain modules/functions/types for future maintainers, add a useful file-level overview, or make a file understandable without tracing its internal logic, even if they do not explicitly say "doc comments.
21change-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.
19structure-review
Review code structure for both unnecessary complexity and insufficient organization. Use whenever the user asks whether code is overengineered, too abstract, too flat, poorly organized, too configurable, too future-proof, whether extra DB columns/fields/helpers should exist, whether a change feels heavier than necessary, whether modules or directories mix unrelated responsibilities, or wants help simplifying or reorganizing code while keeping readability benefits such as clear names, small object boundaries, or helpful file structure.
13planning-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.
11