issue-verify

To verify issue identifiers before referencing them in commit messages, you need an adapter providing get_issue, verify_link, and search_issues endpoints. The Skill confirms existence and entityType, hard-blocking non-issue references to prevent broken citations.

Validating tracker IDs and issue URLs in changelogs or pull requests uses the adapter's verify_link endpoint alongside get_issue calls. This fetches title and status data, requiring explicit user confirmation for unknown or permission-limited responses before allowing citation.

You can batch verify multiple issue references for sprint summaries and migration reports. The Skill surfaces not-found identifiers from the tracker, ensuring bulk reports only cite verified issues that return a valid exists status and entityType.

Yes, issue identifier verification requires an adapter that provides get_issue, verify_link, and search_issues endpoints. These endpoints must return exists and entityType fields, enabling the Skill to enforce hard-blocks on non-issue entities and warn on ambiguous results.

When issue verification returns an ambiguous or unknown result, the Skill warns the user and requires explicit confirmation before proceeding. It hard-blocks references to non-issue entityTypes entirely, preventing incorrect or mis-typed identifiers from entering documentation.

Blocking non-issue entityTypes during issue verification prevents referencing incorrect tracker entries like epics or sub-tasks. The adapter returns entityType data, allowing the Skill to hard-block unsafe references and ensure only valid issues are cited in documentation and commit messages.