skills

Investigate and explain GitHub issues, repo-connected bugs, and user-story issues before an action is chosen. Use when the user asks to “understand this issue,” “find the actual cause,” “compare options,” or “give me a decision memo before we act.” Do not use when the request already chooses an action, including “implement,” “fix,” “make a branch,” “commit,” “push,” or “open a PR”; those tasks should inspect the relevant issue and code without producing Prelude’s full pre-investigation report. Do not use for making code changes or writing an executable plan.md; use visual-coding-plan for plan artifacts after the problem is understood.

Create GitHub-safe and VS Code-safe visual coding project plans in a single plan.md file. Use when asked to plan a coding project, prepare work for a code agent, turn an understood issue or feature request into an executable implementation plan, or make planning notes visually readable without MDX. Do not use for read-only root-cause investigation before the problem is understood; use prelude first. Do not use to execute an existing plan; use assembly.

Stress-test a plan, proposal, architecture, or technical design by interviewing the user one decision at a time. Use when the user asks to be grilled, wants a plan challenged, needs hidden assumptions exposed, wants design trade-offs walked branch by branch, or asks for relentless questioning before implementation.

Opinionated PR and branch review from actual diffs and repository context. Use when the user asks for a PR review, branch review, changed-file review, commit-range review, review comments, unresolved PR thread inspection, CI-aware review, or a thorough code review focused on correctness, maintainability, security, data loss, edge cases, language-specific risks including Python, AI workflow risks, wasted computation, unnecessary abstractions, and missing tests tied to concrete risk.

Execute a local plan.md, commit plan, phase plan, or step-by-step implementation plan in controlled units. Use when the user asks to read or implement a local plan, walk through a commit plan one unit at a time, implement changes phase by phase, validate after each unit, make commits from a plan, leave planning artifacts uncommitted, or continue from a previous plan unit.

create or update github draft pull requests from the current ready branch using git and the github cli. use when the user wants to push the current non-default branch, create a draft pr, update an existing draft pr, or add an update comment to an already published pr. inspect branch state, commits, diff, ./plan.md, pr templates, tests, and existing prs. assume invocation authorizes normal push and gh pr create/edit/comment operations, but refuse on unsafe states such as default branches, staged changes, closed prs, missing gh auth, unclear base branch, non-fast-forward push needs, or required sync unless explicitly requested.