OpenParable
Skip to content
← Back to skills

Worktree completion summary

Productivity

Worktree completion summary is an Agent Skill for productivity published in the IgorWarzocha/howcode repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when Igor says a worktree seems complete and wants a branch/worktree summary saved for later review and merging

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/IgorWarzocha/howcode/blob/HEAD/.pi/workflows/worktree-completion-summary/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/worktree-completion-summary, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Worktree completion summary

Goal

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.

Procedure

  1. Confirm current repo/worktree context:
pwd
git branch --show-current
git rev-parse --show-toplevel
git worktree list --porcelain
  1. Derive:

    • worktree-name from the current repo root basename, e.g. /path/.worktrees/settings_view → settings_view
    • parent-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.
  2. Review the work against the parent branch:

git log --oneline --decorate --max-count=12
git status --short
git diff --stat "$parent_branch...HEAD"
  1. Create the summary file inside the current worktree checkout:
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.

Rules

  • One short paragraph is the default; expand only when the work genuinely needs more context.
  • Do not write a full PR template.
  • Focus on what changed, why it matters, and anything a future merge/review session should know.
  • Do not include test logs unless they affect merge confidence.
  • Write the file in the current worktree, not by switching to or editing the parent checkout.
  • If no separate parent checkout exists, fall back to the current branch name for parent-branch-name.
  • After writing it, tell Igor the file path and keep the chat summary brief.