메뉴
Logs completed epics and significant accomplishments in reverse chronological order. Use after completing major features, releases, or architecture changes to maintain a project changelog.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Audits components and pages for WCAG accessibility issues and suggests fixes. Use when building new UI, reviewing components for a11y compliance, or fixing reported accessibility bugs.
Rewrites text to be clearer, simpler, and more engaging using Scott Adams' writing principles and persuasive techniques. Use when editing marketing copy, blog posts, emails, or any business text that needs to be punchier.
Facilitates solution ideation with clear trade-offs and a final recommendation. Use when exploring architectural decisions, evaluating technology choices, or comparing implementation approaches before writing code.
Reviews code changes for correctness, maintainability, security, and adherence to project conventions. Use when reviewing PRs, auditing recent changes, or getting a second opinion on implementation quality.
Commits staged changes using the conventional commits format with proper type, scope, and description. Use when committing code changes to maintain a clean, standardized git history.
Structured debugging skill for methodical root cause analysis. Use when investigating bugs, unexpected behavior, or errors. Produces an issue summary, key findings, root cause analysis, and recommended solutions without modifying code.
| name | log |
| description | Logs completed epics and significant accomplishments in reverse chronological order. Use after completing major features, releases, or architecture changes to maintain a project changelog. |
Log completed epics using this template in reverse chronological order:
## $date
- $emoji - $epicName - $briefDescription
ChangelogLogger { Scope { LOG ONLY COMPLETED EPICS representing significant user-facing value: - Epic Completions: major feature releases, tool creation, system implementations - User-Impacting Changes: new capabilities, workflows, developer experience improvements - Architecture Decisions: significant refactoring, new patterns, system redesigns }
Boundaries { DO NOT LOG -> config file changes, file organization/moves, minor bug fixes, documentation updates, dependency updates, internal refactoring, test additions/changes, meta-work }
Emojis { 🚀 new feature | 🐛 bug fix | 📝 documentation | 🔄 refactor | 📦 dependency update | 🎨 design | 📱 UI/UX | 📊 analytics | 🔒 security }
Constraints { Always use reverse chronological order (most recent first). Keep descriptions brief (< 50 chars). Focus on epic-level accomplishments, not implementation details. Never log meta-work or trivial changes. Omit the word "epic" from the description. }
Review git changes and any plan diffs to detect recently completed work. }