Skip issue creation for chore/documentation commits in commit-changes and commit-docs #53

New issue

Closed

opened 2026-08-19 00:43:55 +00:00 by david · 1 comment

david commented

2026-08-19 00:43:55 +00:00

Owner

Summary

Update commit-changes and commit-docs so that changes/docs labeled chore or documentation no longer require creating a tracking issue first. feature, bug, and enhancement continue to get an issue as today.

Background

Both skills currently always create a GitHub/Forgejo/GitLab issue before branching, and every downstream artifact (branch name, commit message, PR title, PR body) is issue-number-driven (<type>/issue-<N>/<slug>, issue-<N>: <summary>, Closes #<N>). For low-ceremony chore/docs work this is unnecessary overhead. feature/bug/enhancement should keep full issue tracking.

This also affects the canonical Workflow Conventions text, which is duplicated in three places and must be updated identically in all three:

This repo's own AGENTS.md
furnish-repo's canonical text block (the source of truth it audits/propagates to other repos)
init-project's generated-AGENTS.md template (Phase 5.1)

create-issues is out of scope (different workflow: implementation plans → issues, not working-tree commits).

Decisions

Label scope: chore and documentation skip issue creation. feature, bug, enhancement still get one.
No-issue branch naming: date-based segment instead of issue number, e.g. chore/2025-06-01/bump-deps, documentation/2025-06-01/update-readme (keeps the existing 3-segment shape).
No-issue commit message / PR title: type-prefixed, <type>: <summary> / <type>: <title>, e.g. chore: bump deps.
No-issue PR body: drop the Closes #<N> clause entirely — just the descriptive summary/per-file breakdown.
commit-docs: rewritten as a clean 4-step workflow (branch → commit/push → PR → merge) — no issue references anywhere, since its only label (documentation) never creates an issue.
commit-changes Step 5: "verify issue closed" becomes conditional — runs for feature/bug/enhancement, skipped for chore/documentation (report branch+PR completion only).

Files to update

skills/commit-changes/SKILL.md — conditional issue creation, naming, and Step 5 verify
skills/commit-docs/SKILL.md — full rewrite to clean 4-step workflow, no issue references
AGENTS.md (this repo) — new two-form Workflow Conventions text
skills/furnish-repo/SKILL.md — canonical-text block updated to the new two-form text
skills/init-project/SKILL.md — Phase 5.1 template text updated to the same new two-form text

New canonical Workflow Conventions shape

feature / bug / enhancement → issue-driven: <type>/issue-<N>/<slug>, commit issue-<N>: <summary>, PR title issue-<N>: <title>, PR body Closes #<N>
documentation / chore → no-issue, date-driven: <type>/<YYYY-MM-DD>/<slug>, commit <type>: <summary>, PR title <type>: <title>, PR body has no closing reference

Acceptance Criteria

commit-changes skips issue creation for chore/documentation, uses date-based branch naming, type-prefixed commit/PR titles, no Closes #N in the PR body, and skips Step 5's issue-verify for those labels.
commit-docs is rewritten as a 4-step workflow with zero issue references.
AGENTS.md, furnish-repo's canonical text, and init-project's template all contain the identical updated two-form Workflow Conventions text.
create-issues is untouched.

Non-goals

create-issues skill — out of scope.

## Summary Update `commit-changes` and `commit-docs` so that changes/docs labeled `chore` or `documentation` no longer require creating a tracking issue first. `feature`, `bug`, and `enhancement` continue to get an issue as today. ## Background Both skills currently always create a GitHub/Forgejo/GitLab issue before branching, and every downstream artifact (branch name, commit message, PR title, PR body) is issue-number-driven (`<type>/issue-<N>/<slug>`, `issue-<N>: <summary>`, `Closes #<N>`). For low-ceremony chore/docs work this is unnecessary overhead. `feature`/`bug`/`enhancement` should keep full issue tracking. This also affects the **canonical Workflow Conventions text**, which is duplicated in three places and must be updated identically in all three: - This repo's own `AGENTS.md` - `furnish-repo`'s canonical text block (the source of truth it audits/propagates to other repos) - `init-project`'s generated-`AGENTS.md` template (Phase 5.1) `create-issues` is out of scope (different workflow: implementation plans → issues, not working-tree commits). ## Decisions 1. **Label scope**: `chore` and `documentation` skip issue creation. `feature`, `bug`, `enhancement` still get one. 2. **No-issue branch naming**: date-based segment instead of issue number, e.g. `chore/2025-06-01/bump-deps`, `documentation/2025-06-01/update-readme` (keeps the existing 3-segment shape). 3. **No-issue commit message / PR title**: type-prefixed, `<type>: <summary>` / `<type>: <title>`, e.g. `chore: bump deps`. 4. **No-issue PR body**: drop the `Closes #<N>` clause entirely — just the descriptive summary/per-file breakdown. 5. **commit-docs**: rewritten as a clean 4-step workflow (branch → commit/push → PR → merge) — no issue references anywhere, since its only label (`documentation`) never creates an issue. 6. **commit-changes Step 5**: "verify issue closed" becomes conditional — runs for feature/bug/enhancement, skipped for chore/documentation (report branch+PR completion only). ## Files to update - [ ] `skills/commit-changes/SKILL.md` — conditional issue creation, naming, and Step 5 verify - [ ] `skills/commit-docs/SKILL.md` — full rewrite to clean 4-step workflow, no issue references - [ ] `AGENTS.md` (this repo) — new two-form Workflow Conventions text - [ ] `skills/furnish-repo/SKILL.md` — canonical-text block updated to the new two-form text - [ ] `skills/init-project/SKILL.md` — Phase 5.1 template text updated to the same new two-form text ## New canonical Workflow Conventions shape - `feature` / `bug` / `enhancement` → issue-driven: `<type>/issue-<N>/<slug>`, commit `issue-<N>: <summary>`, PR title `issue-<N>: <title>`, PR body `Closes #<N>` - `documentation` / `chore` → no-issue, date-driven: `<type>/<YYYY-MM-DD>/<slug>`, commit `<type>: <summary>`, PR title `<type>: <title>`, PR body has no closing reference ## Acceptance Criteria - [ ] `commit-changes` skips issue creation for `chore`/`documentation`, uses date-based branch naming, type-prefixed commit/PR titles, no `Closes #N` in the PR body, and skips Step 5's issue-verify for those labels. - [ ] `commit-docs` is rewritten as a 4-step workflow with zero issue references. - [ ] `AGENTS.md`, `furnish-repo`'s canonical text, and `init-project`'s template all contain the identical updated two-form Workflow Conventions text. - [ ] `create-issues` is untouched. ## Non-goals - `create-issues` skill — out of scope.

david added the

enhancement

label

2026-08-19 00:43:55 +00:00

david referenced this issue

2026-08-19 01:02:25 +00:00

53: Skip issue creation for chore/documentation commits in commit-changes and commit-docs #56

david closed this issue

2026-08-19 01:02:27 +00:00

david commented

2026-08-19 01:02:27 +00:00

Author