Jira QA Scope

A manual QA engineer gets a ticket written for developers and a diff they cannot read. What they need is the gap between the two: what the ticket promised, what the team decided later in the comments, and what the code actually changed. This skill closes that gap in words a non-technical tester can act on.

Assumptions

The skill works on these assumptions. Show them to the user in Step 1, so they can correct one before any work starts.

1. Jira is the issue tracker. This is a hard rule. With no working Jira connector, the skill stops in Step 1.
2. The base branch is the repo's default branch (git symbolic-ref --short refs/remotes/origin/HEAD). The user can name another one.
3. Commit subjects and PR titles carry the Jira key (PROJ-123: Fix the thing.). The skill uses the key to find the ticket's commits and merged PRs.
4. The repo glossary can be anywhere. The skill uses the glossary the user or the repo instructions name. If there is none, it uses CONCEPTS.md at the repo root when that file exists. If neither exists, it uses the ticket's own words.
5. The domain is the repo's own. The skill brings no product vocabulary. Every domain word comes from the glossary, the ticket or the code.

Side effects