finalize

# Finalize Implementation Post-implementation QA workflow: tests, code polishing, commit, and self-improvement. ## Task Tracking At the start, use `TaskCreate` to create a task for each phase: 1. Run `/polish-code` skill 2. Run `/simplify-docs` skill 3. Run `/update-changelog` skill 4. Run `/self-improve` skill 5. Ship It ## Phase 1: Run `/polish-code` Skill Run the `/polish-code` skill for the current changes. ## Phase 2: Run `/simplify-docs` Skill Run the `/simplify-docs` skill on the staged changes (`git diff --cached`). Stage any edits it makes before continuing. ## Phase 3: Run `/update-changelog` Skill Run the `/update-changelog` skill. ## Phase 4: Run `/self-improve` Skill Run the `/self-improve` skill for the current session. Always run this phase even if the session seemed routine. ## Phase 5: Ship It ### Step 1: Analyze Split Examine the staged changes and evaluate whether they form a single reviewable unit or several independently reviewable units. This step decides only whether to split; the chosen ship skill owns all repository-state detection and the commit, push, branch, and PR intent. Run `git diff --cached --stat` and `git diff --cached` to understand the scope. Categorize changes along three dimensions: - **Concern type**: refactoring, bug fix, new feature, cleanup, dependency update - **Layer/domain**: backend, frontend, database migrations, i18n, tests, configuration - **Logical unit**: files that form a coherent, independently reviewable ...