菜单
Iterate on UI visuals by editing code, hot reloading, capturing screenshots, and refining in loops.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Commit task changes from a worktree onto the base branch (read from KANBAN_BASE_BRANCH env var). Use when finishing a kanban task to stage, commit, and cherry-pick changes back to the base ref.
Recover orphaned/dangling commits from kanban headless runs where the AI agent committed in the worktree but the kanban-commit agent failed to cherry-pick to the target branch (commit exists as a dangling object unreachable from any ref). Use when a ai-task-start-kanban-headless run completed/finished but the commit is missing from the target branch, or when investigating "nothing to commit — working tree is clean" in kanban-commit agent output.
Capture a new feature, bug, or tweak idea as an issue file in the project's kanban repo at <project>-kanban/issues/<id>-<slug>.backlog.md. Runs a short grilling pass against the existing domain model so the entry is sharper than a one-liner. Uses sequential IDs (via flock(1)) so files sort naturally even with concurrent agents.
Plan and execute a full git history squash job — analyze commits between two refs, group them into ~10 semantically meaningful squashes, drop irrelevant directories or paths, cherry-pick each group with conflict resolution onto a new branch, and verify the final tree matches the original modulo dropped paths. Use when the user says "reduce commits", "squash branch history", "clean up git history", "rewrite branch", "compress commits", or wants to consolidate a messy branch before merge.
DEPRECATED — The backlog/issue distinction no longer exists. All work items are issues (<project>-kanban/issues/<id>-<slug>.<state>.md) from creation. Use backlog-add to capture an issue, to-prd to create a PRD. This skill is kept for reference only.
Read the last pi agent session for the current project, extract what was discussed or done, and create issue files (as <project>-kanban/issues/<id>-<slug>.backlog.md) for any work items, bugs, or follow-ups it uncovered. Use when a session ended without wrapping everything up, when the user wants to capture session outcomes, or when you need to preserve context across sessions.
| name | ui-iteration |
| description | Iterate on UI visuals by editing code, hot reloading, capturing screenshots, and refining in loops. |
| metadata | {"short-description":"Visual UI iteration loop with screenshots and mock states."} |
Use this skill when the user wants iterative UI refinements with live preview and screenshots.
Core loop (repeat until objectives are met):
Requirements:
TEST-YYYYMMDD-HHMMSS.png) so progress is traceable.Mocking guidance:
Screenshot notes:
Tooling and command usage (examples):
date +%Y%m%d-%H%M%Sscripts/flutter-runctl reload -d <DEVICE_ID> -t rscripts/device-screenshot take_screenshot <DEVICE_TARGET> /full/path/TEST-<TIMESTAMP>.pngIf the user supplies different tooling or a different platform, replace the above with their commands.
Finish criteria: