showdar-gitlisted

# Showdar Git ## Purpose Complete local Git workflows with evidence, narrow ownership, and a verifiable handoff. This skill owns repository state transitions, not source-code review or GitHub administration. ## When to use - The user asks to inspect Git state or finish a local Git workflow. - A task needs selective staging, a commit, branch switching, merging, rebasing, or cherry-picking. - A merge, rebase, or cherry-pick has conflicts. - The user explicitly asks to push, pull, or remove a safely merged branch. - A previous Git operation was interrupted and repository state is ambiguous. ## When not to use - Use `showdar-review` for reviewing implementation quality or a diff without a Git mutation. - Use `showdar-ship` for delivery-readiness verification; Ship does not imply Git mutation. - Use `showdar-recover` for an interrupted coding task when Git itself is not the recovery boundary. - Use `showdar-debug` for a source defect, test failure, or runtime regression. - Do not turn a local Git request into GitHub, CI/CD, deployment, or release work. ## Inputs and assumptions - The repository path, current branch, requested operation, and target branch are known or inspectable. - The working tree may contain user changes that are unrelated to the current task. - Existing repository instructions and commit-message conventions are authoritative. - A remote is evidence only; its presence does not authorize a remote mutation. - A published/shared branch is treated as history