issue-editing

What problem does it solve?

Prevents stale, conflicting, or hallucinated edits to existing issues by enforcing a fetch-before-edit workflow and validating field changes before mutation. It reduces race conditions, accidental overwrites, and edits based on guessed identifiers.

Core Features & Use Cases

• Fetch-before-edit enforcement: Always call get_issue and use the returned state as the authoritative base before updating.
• Field validation: Verify status, assignee identifiers, labels, priorities, titles, and descriptions against platform-specific rules.
• Concurrent edit detection: Check updatedAt timestamps and surface recent modifications with options to proceed, refetch, or cancel.
• Workflow guardrails: Block edits of non-issue entities, prevent fabricated identifiers, and require valid status transitions.
• Use Cases: Updating issue status or assignee, bulk-updating labels, editing titles/descriptions, and post-edit verification.

Quick Start

Fetch the current issue state with get_issue, confirm exists and entityType is "issue", then apply the intended status and assignee updates only after validation.