Skip to content

Update core commands to use formatIssueId #598

@NoahCardoza

Description

@NoahCardoza

Summary

Migrate commands that have IssueTracker access via dependency injection to use formatIssueId instead of hardcoded # prefixes.

Context

Part of Epic #595. These commands already have an IssueTracker instance available, so they can call this.issueTracker.formatIssueId(id) directly.

Files to Modify

  • src/commands/start.ts — Replace #${parsed.number} with this.issueTracker.formatIssueId(parsed.number) (~4 sites)
  • src/commands/finish.ts — Same pattern (~3 sites, plus sites using issuePrefix from MCP provider)
  • src/commands/enhance.ts — Same (~2 sites)
  • src/lib/IssueEnhancementService.ts — Same (~2 sites, has injected IssueTracker)
  • src/lib/LoomLauncher.ts — Replace Issue #${identifier} formatting (~2 sites, needs provider access added or use static utility)

Acceptance Criteria

  • All hardcoded # prefixes in the listed files are replaced with formatIssueId calls
  • Test files updated to expect provider-formatted output
  • For GitHub-provider tests, expected output remains unchanged (still #123)
  • At least one Jira or Linear test case added where practical
  • pnpm build passes
  • pnpm test passes

Scope Boundaries

  • Do NOT change PR references (PR #X) — PRs are GitHub-only
  • Do NOT change debug-level messages
  • Do NOT change files covered by Issues 3, 4, or 5

Dependencies

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions