qa-scope SKILL.md skillA
qa-scope from alexander-danilenko/cortex-ai-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add alexander-danilenko/cortex-ai-skills/qa-scope@git:20261020.54790c2Pins git:20261020.54790c2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- alexander-danilenko/cortex-ai-skills
- Path
plugins/engineering/cortex-jira/skills/qa-scope/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261020.54790c2, committed Oct 20, 2026
- First version recorded
- Oct 13, 2026
- Size
- 17,408 bytes
- Repository stars
- 17
- License
- MIT
Draft the QA scope and plain-language test scenarios for a Jira ticket — brief one-liners with automated test references by default, or full Given/When/Then steps — built from the full ticket, the decisions made in its comments, and the actual code change read commit by commit (open PR, the ticket's merged PR, the branch against its base, or a named commit range). Saves a Markdown draft under docs/, iterates with the user, then posts it to the ticket as a new Jira comment only after explicit…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 every `CONTEXT.md`, `CONCEPTS.md` or `GLOSSARY.md` at the repo root or under `docs/`. If none exists, it uses the ticket's own words. …
Read the whole file at its exact version.
How to install
mdr add alexander-danilenko/cortex-ai-skills/qa-scope@sha256:79f5d17192803771The line at the top of this page pins the label git:20261020.54790c2, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_dwm463j4asrcmhcd)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 13, 2026 and Oct 20, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.54790c2 latest | 2026-10-20 | 54790c2 | 17,408 B | A | view · diff |
| git:20261020.adab63f | 2026-10-20 | adab63f | 16,407 B | A | view · diff |
| git:20261013.ecfffa1 | 2026-10-13 | ecfffa1 | 14,206 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (17408 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
alexander-danilenko/cortex-ai-skills · 17 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dwm463j4asrcmhcd GET https://markdownregistry.com/api/v1/resolve?ref=alexander-danilenko/cortex-ai-skills/qa-scope GET https://markdownregistry.com/api/v1/blob/79f5d17192803771856238ef1d9c93003207115ac71b9a15572ad0c0c535d823
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from alexander-danilenko/cortex-ai-skills
Every file in alexander-danilenko/cortex-ai-skills