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 `/update-changelog` skill 3. Run `/self-improve` skill 4. Ship It ## Phase 1: Run `/polish-code` Skill Run the `/polish-code` skill for the current changes. ## Phase 2: Run `/update-changelog` Skill Run the `/update-changelog` skill. ## Phase 3: Run `/self-improve` Skill Run the `/self-improve` skill for the current session. Always run this phase even if the session seemed routine. ## Phase 4: Ship It ### Step 1: Analyze Split Examine the staged changes and evaluate whether they should be split into multiple commits, branches, and PRs for reviewability. Detect the repository's default branch via `gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'`. Check the current branch name and whether a PR already exists for it using `gh pr view`. If a PR exists, read its title and description to understand the branch's purpose. This context informs which changes belong on the current branch and which should be split off. 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**: file...