kai-git-workflow SKILL teaches bare closes #N; align with live Forgejo-URL closes-issue gate #168

New issue

Closed

opened 2026-06-04 10:26:14 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-04 10:26:14 +00:00

Owner

Problem

kai-git-workflow/SKILL.md still tells agents to close a same-repo issue with a
bare closes #N / fixes #N / resolves #N:

Every commit closes a same-repo issue. File first, then commit with closes #N / fixes #N / resolves #N.

But the closes-issue commit-msg gate (this repo's agentic_os/check_commit_closes_issue.py,
live since v0.13.0) now rejects bare #N and owner/repo#N and requires
the full Forgejo issue URL. On a GitHub-mirrored repo a bare closes #N is a
GitHub closing keyword and silently closes whatever GitHub issue holds number N,
a different tracker than the canonical Forgejo one whose numbers diverge.

So agents following this skill hit the gate error on commit. The doc teaches the
form the gate forbids.

Fix

Update the kai-git-workflow/SKILL.md line to teach the Forgejo URL closing form
(closes https://forgejo.coilysiren.me/<owner>/<repo>/issues/N) and note that
repos whose canonical tracker is GitHub still use closes #N (per the
github-issue-tracker reference). Pure doc alignment with the already-live gate;
no gate change.

Out of scope (separate follow-ups)

coding-gish is obsolete on a deeper axis: it tells agents to file a GitHub
issue via coily ops gh issue create, which coily now hard-blocks, and to
close with bare closes #N. That needs a Forgejo migration rewrite, not a
one-line swap.
catalog-trifecta still mandates the bare owner/repo#N cross-reference
citation in AGENTS footers - the same form the closes-issue gate forbids in
commit messages. Aligning that fleet-wide convention is a gate flip that needs
sign-off.

## Problem `kai-git-workflow/SKILL.md` still tells agents to close a same-repo issue with a bare `closes #N` / `fixes #N` / `resolves #N`: > - Every commit closes a same-repo issue. File first, then commit with `closes #N` / `fixes #N` / `resolves #N`. But the `closes-issue` commit-msg gate (this repo's `agentic_os/check_commit_closes_issue.py`, live since v0.13.0) now **rejects** bare `#N` and `owner/repo#N` and **requires** the full Forgejo issue URL. On a GitHub-mirrored repo a bare `closes #N` is a GitHub closing keyword and silently closes whatever GitHub issue holds number N, a different tracker than the canonical Forgejo one whose numbers diverge. So agents following this skill hit the gate error on commit. The doc teaches the form the gate forbids. ## Fix Update the `kai-git-workflow/SKILL.md` line to teach the Forgejo URL closing form (`closes https://forgejo.coilysiren.me/<owner>/<repo>/issues/N`) and note that repos whose canonical tracker is GitHub still use `closes #N` (per the `github-issue-tracker` reference). Pure doc alignment with the already-live gate; no gate change. ## Out of scope (separate follow-ups) - `coding-gish` is obsolete on a deeper axis: it tells agents to file a GitHub issue via `coily ops gh issue create`, which coily now hard-blocks, and to close with bare `closes #N`. That needs a Forgejo migration rewrite, not a one-line swap. - `catalog-trifecta` still mandates the bare `owner/repo#N` cross-reference citation in AGENTS footers - the same form the closes-issue gate forbids in commit messages. Aligning that fleet-wide convention is a gate flip that needs sign-off.

coilysiren referenced this issue

2026-06-04 10:29:32 +00:00

main is red: documentation-layout rejects all commits (tooling-issue-prioritization 4174 > 4000 cap, regressed by 5f9cd1d) #169

coilysiren added the

label

2026-06-17 07:05:21 +00:00

coilysiren commented

2026-06-17 08:23:07 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:23:07 +00:00