القائمة
Use when Igor says a worktree seems complete and wants a branch/worktree summary saved for later review and merging
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Deprecated. Howcode now uses regular Pi SDK extensions from Pi settings/packages; do not add Howcode-only native extension snapshots or settings. Use this only as historical context when removing old dual-native-extension code.
Use when weird app/UI behavior needs live reproduction and tracing, including flicker, stale state, remounts, focus/scroll jumps, action glitches, or ordering flashes
TypeScript/JavaScript codebase hardening: maintainability, code quality, architecture cleanup, repo scoring, agent-friendly structure, godfiles, godfunctions, feature folders, DRY, type safety, traversability, feedback loops, worktrees, subagents, swarm refactors.
Runs this repo's GitHub issue and PR workflow with gh. Use when the user mentions issue numbers, PR links, or the project board, asks to pick a manageable issue, wants an issue rewritten into a proper issue, wants backlog triage or relabeling, or wants a PR opened, updated, or reviewed. Do not use for local-only git work with no GitHub issue or project flow.
Use when Igor asks to build this branch/current repo and run a disposable build version
How to add short-lived static fixtures for hard-to-reproduce UI states while tuning layout
| name | Worktree completion summary |
| description | Use when Igor says a worktree seems complete and wants a branch/worktree summary saved for later review and merging |
Create a short, useful summary file in the current worktree at:
branches/(parent-branch-name)/(worktree-name).md
These files live in each worktree until that worktree is merged, so future sessions can review all completed worktrees for a parent branch in one place before merging.
pwd
git branch --show-current
git rev-parse --show-toplevel
git worktree list --porcelain
Derive:
worktree-name from the current repo root basename, e.g. /path/.worktrees/settings_view → settings_viewparent-branch-name from the main/parent checkout in git worktree list --porcelain, not from the current worktree branch. In this repo that is usually the worktree at /home/igorw/Work/howcode.Review the work against the parent branch:
git log --oneline --decorate --max-count=12
git status --short
git diff --stat "$parent_branch...HEAD"
mkdir -p "branches/$parent_branch"
Write a concise paragraph describing what was accomplished and why it matters. Keep it PR-ish, but not a full PR body.
Example:
Reorganized Settings into clearer user-facing categories, grouped all Pi-backed settings under a single Pi section, and fixed worktree Biome checks so this branch can be reviewed and merged cleanly.
parent-branch-name.