菜单
Logs completed epics and significant accomplishments in reverse chronological order. Use after completing major features, releases, or architecture changes to maintain a project changelog.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/iulspop/aidd-skills --skill log命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Continuously steers the codebase toward the VISION.md. Reads the vision, assesses current state, picks the highest-impact next action, builds with TDD, commits, and repeats. Never stops. Use when you want autonomous, vision-driven development.
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.
正在显示 SKILL.md
基于 SOC 职业分类
| 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. }