operation-gitlisted

# operation-git Centralized git + GitHub operations. We follow **GitHub Flow**: `main` is protected and always deployable, and all feature work happens on short-lived branches that merge back via pull request. Workflow skills (`workflow-e2e-*`, `workflow-engineer-*`, `workflow-reviewer-*`), the `implement-slice` Workflow script, and the `/implement-feature` command never duplicate `gh` / `git` plumbing — they call the scripts under this skill's `scripts/` directory. (Outer-loop candidate discovery for `/implement-feature` lives entirely as scripts here too — `task-finder.sh` + the four stage scripts: reconcile (0), kickoff-slice (1), fix-pr (8), close-pr (9) — with no agent or skill layer in between. The inner slice cycle runs inside the per-slice `implement-slice` Workflow, not here.) ## When to activate Activate this skill whenever the user: - Asks for help writing a commit message, branch name, PR title/body, or issue. - Is about to create, name, or push a branch — including worktrees. - Wants to open, update, or merge a pull request. - Wants to create or label an issue, link a blocker, or close one. - Is preparing a release, bumping a version, or tagging. - Edits or creates a `.gitignore`. - Asks "how do I do X with `gh`" or wants the standard GitHub CLI invocation for a task. Also load this skill implicitly from inside any `workflow-*` skill that needs to mutate GitHub state — the `workflow-*` skill drives the workflow, this skill owns the primitives. Do NOT activa