Home / alexander-danilenko / cortex-claude-code-plugins · GitHub

qa-scope SKILL.md skillA

qa-scope from alexander-danilenko/cortex-claude-code-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add alexander-danilenko/cortex-claude-code-plugins/qa-scope@git:20261013.ecfffa1

Pins git:20261013.ecfffa1 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: alexander-danilenko/cortex-claude-code-plugins
Path: plugins/engineering/cortex-jira/skills/qa-scope/SKILL.md
Versions recorded: 1
Latest version: git:20261013.ecfffa1, committed Oct 13, 2026
Size: 14,206 bytes
Repository stars: 17
License: MIT

Draft the QA scope and plain-language Given/When/Then test scenarios for a Jira ticket, 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 approval. Use on "QA scope for PROJ-123", "what should QA test…

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 `CONCEPTS.md` at the repo root when that file exists. If neither exists, it uses the ticket's own words.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add alexander-danilenko/cortex-claude-code-plugins/qa-scope@sha256:4e63a16fc9b539f3

The line at the top of this page pins the label git:20261013.ecfffa1, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_ydlplzo7pp6xsrky.svg)](https://markdownregistry.com/a/art_ydlplzo7pp6xsrky)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Oct 13, 2026.

version	committed	commit	size	audit
git:20261013.ecfffa1 latest	2026-10-13	ecfffa1	14,206 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (14206 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

GitHub

alexander-danilenko/cortex-claude-code-plugins · 17 stars · license MIT · pushed 2026-10-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ydlplzo7pp6xsrky
GET https://markdownregistry.com/api/v1/resolve?ref=alexander-danilenko/cortex-claude-code-plugins/qa-scope
GET https://markdownregistry.com/api/v1/blob/4e63a16fc9b539f3b36e9f8123124df3de8115c31882f29aac4c15e1c01c7d5c

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-claude-code-plugins

CLAUDE.md CLAUDE.md file

alexander-danilenko/cortex-claude-code-plugins · CLAUDE.md

git:20261013.35be08e · audit A · 17 stars

answer-buzzkill SKILL.md skill

alexander-danilenko/cortex-claude-code-plugins · plugins/common/cortex-communication/skills/answer-buzzkill/SKILL.md · Write a short, fact-checked reply that answers a colleague's question in one meaning only, ready to copy and paste. The…