issue-105: serialize issue creation with 3s pacing #106

Merged

david merged 1 commit from feature/issue-105/serialize-issue-creation into main

2026-08-28 11:56:20 +00:00

david commented

2026-08-28 11:32:50 +00:00

Owner

Closes #105

What

Updates skills/create-issues/SKILL.md so the agent serializes issue/milestone creation and waits 3 seconds after each create, preventing race conditions that produce non-sequential issue numbers.

Why

When the agent fires several issue-create calls in one parallel tool block, the host assigns issue numbers in non-deterministic order (observed on Forgejo: a later step ending up with a lower number than an earlier one). A post-create sleep alone does not fix this — creates must also be serialized, one per turn, so no two creates are in flight at once.

Changes

Phase 6.3 — new bolded Serialization and pacing subsection:
- One create per turn (never batch multiple milestone/issue creates in one parallel tool block).
- Wait 3 seconds after each create (e.g. bash sleep 3) before issuing the next.
- Applies to all three hosts (Forgejo, GitHub, GitLab) and to milestone creates as well as issue creates (a just-created milestone may not be visible immediately).
- Phase 6.4 backfill edits are exempt (they are edits, not creates).
Quick Reference — one line summarizing the pacing rule.

Notes

Hardcoded 3s constant — no config plumbing.
Validation deferred to the next real create-issues run (no dedicated test).
Per AGENTS.md, merging is the repo owner's decision.

Closes #105 ## What Updates `skills/create-issues/SKILL.md` so the agent **serializes** issue/milestone creation and **waits 3 seconds after each create**, preventing race conditions that produce non-sequential issue numbers. ## Why When the agent fires several issue-create calls in one parallel tool block, the host assigns issue numbers in non-deterministic order (observed on Forgejo: a later step ending up with a lower number than an earlier one). A post-create sleep alone does not fix this — creates must also be serialized, one per turn, so no two creates are in flight at once. ## Changes - **Phase 6.3** — new bolded **Serialization and pacing** subsection: - One create per turn (never batch multiple milestone/issue creates in one parallel tool block). - Wait **3 seconds** after each create (e.g. `bash sleep 3`) before issuing the next. - Applies to **all three hosts** (Forgejo, GitHub, GitLab) and to **milestone creates as well as issue creates** (a just-created milestone may not be visible immediately). - Phase 6.4 backfill edits are exempt (they are edits, not creates). - **Quick Reference** — one line summarizing the pacing rule. ## Notes - Hardcoded 3s constant — no config plumbing. - Validation deferred to the next real create-issues run (no dedicated test). - Per AGENTS.md, merging is the repo owner's decision.

david added the

enhancement

label

2026-08-28 11:32:50 +00:00

david added 1 commit

2026-08-28 11:32:51 +00:00