Skip to content

Use issue number (not issue ID) in task prompt text#119

Merged
neekolas merged 1 commit intoxmtplabs:mainfrom
xmtp-coder-agent:fix/issue-117
Apr 21, 2026
Merged

Use issue number (not issue ID) in task prompt text#119
neekolas merged 1 commit intoxmtplabs:mainfrom
xmtp-coder-agent:fix/issue-117

Conversation

@xmtp-coder-agent
Copy link
Copy Markdown
Collaborator

@xmtp-coder-agent xmtp-coder-agent commented Apr 21, 2026

Summary

  • Swap issue.idissue.number in the ai_prompt block produced by buildTemplateInputs.
  • Rename the label from ISSUE_ID: to ISSUE_NUMBER: so the downstream /coder-task skill receives the user-facing issue number.
  • Update the create-task.test.ts fixture assertion to expect ISSUE_NUMBER: 42.

Resolves #117

Test plan

  • npm run check (typecheck + lint + format + 373 tests) passes locally
  • CI green

🤖 Generated with Claude Code

Note

Replace issue ID with issue number in AI task prompt text

Changes the buildAiPrompt function in template-inputs.ts to use issue.number instead of issue.id, renaming the prompt field from ISSUE_ID to ISSUE_NUMBER. The BuildTemplateInputsParams interface and create-task.ts are updated to match. Behavioral Change: generated ai_prompt strings now contain ISSUE_NUMBER: <number> instead of ISSUE_ID: <id>, which are different values since GitHub issue numbers and internal IDs are not the same.

Macroscope summarized d124265.

The `ai_prompt` block composed by `buildTemplateInputs` previously
embedded GitHub's numeric `issue.id` under an `ISSUE_ID:` label. The
downstream `/coder-task` skill expects the user-facing issue number,
so swap the field and rename the label to `ISSUE_NUMBER:`.

Resolves xmtplabs#117

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@neekolas neekolas marked this pull request as ready for review April 21, 2026 13:50
@neekolas neekolas merged commit 0a6ddd9 into xmtplabs:main Apr 21, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use issue number and not issue ID

2 participants