renanliberato

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.

ELIMINATED — Issues are created directly via backlog-add or manually. PRDs reference issues by ID in their frontmatter. This file is kept for reference.

Turn the current conversation context into a PRD with its own sequential ID and save it as <project>-kanban/prds/<id>-<slug>.md. Preserves history — old PRDs are never overwritten, they coexist. Use when user wants to create a PRD from context.

Use when you need an isolated copy of a large repository — especially a Unity project — for an agent task, parallel work, or a risky experiment, and a full git worktree or plain copy is too expensive (slow, many GB of disk, or a forced Unity reimport). macOS/APFS only.

Iterate on UI visuals by editing code, hot reloading, capturing screenshots, and refining in loops.

Create and manage issues in the kanban repo. Create new issues (investigator) or pick and implement backlog items (tackle-worker).

Edit squashed commits on main by unfolding micro-commits into a working branch, mutating them with normal git operations (rebase -i, amend, cherry-pick, commit), then re-squashing. Use when the user mentions "git subcommit", "subcommit", "unfold", "resquash", wants to edit a squashed commit, drop/add/edit individual commits inside a squashed commit, or says "edit the commit on main hash using git subcommit".

Bootstrap quality-gate convention scripts (quality-gate-tests and quality-gate-linter) for a project. Detects the project's language and tooling, then generates appropriate wrapper scripts. Use when setting up the quality gate in a new project or when validate reports missing scripts.

Review and respond to mdreview comment threads (`<!-- mdreview-comments: -->` blocks) in markdown files via the `mdreview` CLI.