coding-core-git-workflow: a pushed branch always gets a PR

coilyco-ops commented

2026-08-08 02:54:33 +00:00

Owner

Problem

coding-core-git-workflow defines four lanes but never states what happens when no lane is resolved. In an interactive session with no assigned workflow, an agent can push a task branch, report the branch name, and stop. The work is then invisible: nothing surfaces it for review, nothing tracks it, and it decays into an orphan ref.

Kai's ruling, verbatim in spirit: a branch without a PR is just litter.

Observed on coilyco-gaming/sirens-echo thread-scoped replies. The agent pushed feat/thread-scoped-replies, reported the branch, and waited. The correction was immediate and the PR (sirens-echo#78) had to be opened as a follow-up turn.

Why the current text permits it

The lane list reads as four peers:

direct-to-main - commit to main directly, then push.
pull-request - push a branch and open a human-gated Forgejo PR.
pull-request-and-merge - push a branch and mark the PR for the director merge lane.
remote-branch-only - push a branch and stop. No PR and no merge.

remote-branch-only is a real lane with a real purpose, so branch-and-stop looks like an available default rather than an explicitly-resolved exception. Nothing names pull-request as the fallback when the caller assigned nothing.

Fix

Add one bullet after the lane list stating that a pushed branch always gets a PR, that remote-branch-only is the sole exception and applies only when the caller resolved that lane, and that unassigned work defaults to pull-request.

Constraint

.agents/composed/coding-core-git-workflow/COMPOSED.md is 3742 chars against the 4000-char per-source cap. The addition has to fit in roughly 250 chars, which is enough for one terse bullet and nothing more.

Worth noting separately: that file has under 300 chars of headroom left. The next substantive addition to this skill will need either a cap bump or a split into references/.

## Problem `coding-core-git-workflow` defines four lanes but never states what happens when no lane is resolved. In an interactive session with no assigned workflow, an agent can push a task branch, report the branch name, and stop. The work is then invisible: nothing surfaces it for review, nothing tracks it, and it decays into an orphan ref. Kai's ruling, verbatim in spirit: a branch without a PR is just litter. Observed on `coilyco-gaming/sirens-echo` thread-scoped replies. The agent pushed `feat/thread-scoped-replies`, reported the branch, and waited. The correction was immediate and the PR (sirens-echo#78) had to be opened as a follow-up turn. ## Why the current text permits it The lane list reads as four peers: - `direct-to-main` - commit to `main` directly, then push. - `pull-request` - push a branch and open a human-gated Forgejo PR. - `pull-request-and-merge` - push a branch and mark the PR for the director merge lane. - `remote-branch-only` - push a branch and stop. No PR and no merge. `remote-branch-only` is a real lane with a real purpose, so branch-and-stop looks like an available default rather than an explicitly-resolved exception. Nothing names `pull-request` as the fallback when the caller assigned nothing. ## Fix Add one bullet after the lane list stating that a pushed branch always gets a PR, that `remote-branch-only` is the sole exception and applies only when the caller resolved that lane, and that unassigned work defaults to `pull-request`. ## Constraint `.agents/composed/coding-core-git-workflow/COMPOSED.md` is 3742 chars against the 4000-char per-source cap. The addition has to fit in roughly 250 chars, which is enough for one terse bullet and nothing more. Worth noting separately: that file has under 300 chars of headroom left. The next substantive addition to this skill will need either a cap bump or a split into `references/`.

coilyco-ops referenced this issue from a commit

2026-08-08 02:55:53 +00:00

docs(skills): a pushed branch always gets a PR

coilyco-ops referenced this issue from a pull request that will close it,

2026-08-08 02:56:10 +00:00

docs(skills): a pushed branch always gets a PR #973