Menu
Use when the user asks to refresh documentation for the unic repository after code changes, shipped features, milestone progress, or README drift. Do not use for feature implementation or PR shipping.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user asks to run unic locally, capture TUI screenshots, review the Bubble Tea UX, suggest UX improvements, or optionally implement scoped UX polish in the unic repository. This skill is for terminal UI review and safe UX iteration, not for unrelated feature work, dependency updates, PR shipping, or non-UX code review.
Use when the user asks to update, bump, refresh, audit, or modernize dependencies, libraries, Go modules, the Go language version, or Go toolchain support in the unic repository. Use for dependency maintenance PRs, safe patch/minor Go module updates, Go version bumps, vulnerability-driven dependency updates, or CI/doc updates tied to dependency or Go version changes. Do not use for unrelated feature work, docs-only edits, or CI refactors unless they are required by the dependency/toolchain update.
Use when the user asks to implement a feature, milestone item, or GitHub issue in the unic repository, especially new AWS service work. Do not use for pure refactors, docs-only updates, PR shipping, or issue triage.
Use when the user asks to implement refactors from a prior unic senior review report. Do not use for new features or behavior changes.
Use when the user explicitly asks to stage, commit, push, and open a pull request for unic. Do not use for general coding work or docs-only sync unless the user is asking to ship the current branch.
Use when the user asks to create GitHub issues from planned but unimplemented unic work in PLAN.md. Do not use for editing existing issues or for implementation.
| name | unic-update-docs |
| description | Use when the user asks to refresh documentation for the unic repository after code changes, shipped features, milestone progress, or README drift. Do not use for feature implementation or PR shipping. |
Update unic documentation so the checked-in docs match the current repo
state.
README.md and PLAN.md.git log --oneline -10.gh issue view <number> or gh pr view <number>.gh issue list --state open --limit 50 to align the docs with the actual
backlog.README.md to match shipped behavior.Currently Implemented Features accurate.TUI Key Bindings when shortcuts changed.Usage when commands or flags changed.Configuration when config shape or precedence changed.PLAN.md when roadmap state changed.Summarize what documentation changed and call out any remaining mismatches you could not resolve from the current repo state.