agentic-qa-boilerplate

In the author's own words, from each skill's SKILL.md.

• acli

  Atlassian CLI (official `acli` binary) for Jira Cloud, Confluence Cloud, and org admin tasks from the terminal. Use whenever the user wants to create, view, edit, transition, assign, clone, archive, comment on, link, or bulk-operate on Jira work items; list or manage projects, boards, sprints, filters, dashboards, or custom-field definitions; create or update Confluence spaces, pages, or blog pos…

  .agents/skills/acli/SKILL.md on GitHub (opens in a new tab)

• agentic-qa-core

  Foundation skill that hosts shared references cited by other workflow skills (briefing template, dispatch patterns, orchestration doctrine, skill composition strategy). Loaded on demand by any skill that declares `agentic-qa-core` in its Dependencies block. Do NOT use for: adapting KATA tests (use `/test-framework-adaptation`), or onboarding the target project (use `/project-discovery`).

  .agents/skills/agentic-qa-core/SKILL.md on GitHub (opens in a new tab)

• agentic-qa-onboard

  Walks new users through this repo's QA flow — Playwright + KATA + Allure + Xray stack, Jira QA state machine (statuses read from `.agents/jira-workflows.json`, never from memory), the IQL stages by name, /shift-left-testing for pre-sprint AC refinement on backlog Stories, /sprint-testing for in-sprint manual QA, /test-documentation for TMS test cases, /test-automation for KATA-compliant E2E/API t…

  .agents/skills/agentic-qa-onboard/SKILL.md on GitHub (opens in a new tab)

• bug-screenshot-annotation

  Turns a raw bug screenshot into a QA-style annotated evidence image — circles/ovals around the broken region, arrows, callout text boxes, a 'BUG — <KEY>' corner badge, and axis tick-marks for date/offset bugs. Use whenever a bug is visual or positional (overlapping elements, misalignment, wrong date/offset on a chart axis, a UI element in the wrong place) and a plain screenshot would need a parag…

  .agents/skills/bug-screenshot-annotation/SKILL.md on GitHub (opens in a new tab)

• business-api-context

  What the API of the system under test MEANS to the business: every endpoint group, who calls it and why, what it changes, which auth level and role it needs, the business flows that cross several endpoints, error semantics and the external integrations behind them. Load it whenever a task touches an API test, a request or response, an auth or permission question, a status code that looks wrong, c…

  .agents/skills/business-api-context/SKILL.md on GitHub (opens in a new tab)

• business-data-context

  What the system under test IS at the data level: business entities and why they exist, their relationships, state machines, automatic processes (DB triggers, cron jobs, webhooks), external integrations and the business flows that move data between them. Load it whenever a task touches the database, data validation, a SQL query, test data setup, an entity's lifecycle or status transitions, a trigg…

  .agents/skills/business-data-context/SKILL.md on GitHub (opens in a new tab)

• business-domain-context

  The vocabulary and the business of the system under test: what the product is for, who pays and why, and what every domain term means (the business meaning, the label the UI shows, the identifier the code uses, how it relates to other terms). Load it whenever a task names, labels or explains a domain concept: writing or refining acceptance criteria, authoring an ATP, naming a test case or a test…

  .agents/skills/business-domain-context/SKILL.md on GitHub (opens in a new tab)

• business-e2e-context

  How people actually use the system under test end to end: the personas, the user journeys first (entry point, steps, branches, where money or data changes hands, where it can fail), then the feature catalog those journeys cross and the flows that span several features. Load it whenever a task touches an E2E or UI test, a user flow, a smoke or regression scope, an exploratory session, a story's pl…

  .agents/skills/business-e2e-context/SKILL.md on GitHub (opens in a new tab)

• evidence-artifact

  Turns a ticket's test evidence into ONE private claude.ai page (an Artifact) that a developer or PM can open and read: a verdict header, the build under test, a board of test cases and bugs, and a full-window viewer per case with annotated screenshots (marks drawn from the element's real box), expected/actual compare, API requests, SQL results and timelines. One page per story ticket under test p…

  .agents/skills/evidence-artifact/SKILL.md on GitHub (opens in a new tab)

• exploratory-testing

  Ticket-free exploratory testing of a critical flow, a module or the whole product, across UI, API and DB together, in the Execution stage. Runs a charter, a parallel reconnaissance fan-out, a refutation pass whose job is to kill each finding, a main-thread tie-break, and a handoff where every candidate scenario is executed live, marked NEW / WEAK / COVERED against existing coverage (the coverage…

  .agents/skills/exploratory-testing/SKILL.md on GitHub (opens in a new tab)

• framework-development

  Framework evolution mode — evolves the QA boilerplate itself (KATA, fixtures, cli/, scripts/, api/schemas/ pipeline, package.json deps). Self-contained Plan → Code → Verify → Archive pipeline; needs nothing outside the repo (no SDD-* skills). Use when adding new fixture APIs, refactoring KATA base classes, evolving the installer, modifying the OpenAPI sync pipeline, or any change to the framework…

  .agents/skills/framework-development/SKILL.md on GitHub (opens in a new tab)

• git-flow-master

  End-to-end Git operator for any branching strategy. Auto-detects the project's strategy (solo-main, main+integration, enterprise multi-branch, trunk-based, GitFlow, GitHub Flow, GitLab Flow, SDET integration-trunk for chained test-automation suites) from .git config, branches, and the `git_strategy:` block in `.agents/project.yaml`, then adapts every commit, branch, push, PR, conflict-fix, and ch…

  .agents/skills/git-flow-master/SKILL.md on GitHub (opens in a new tab)

• infra-context

  How the system under test is built, run and deployed: its architecture and external services, the backend and frontend stacks with their run and test commands, the auth flow, the environments and their URLs, the CI/CD pipelines, and the non-functional budgets it must hold (performance, security, reliability, observability). Load it whenever a task wires the test framework to the stack, touches an…

  .agents/skills/infra-context/SKILL.md on GitHub (opens in a new tab)

• iql-context

  The methodology index of this repo: how the IQL (Integrated Quality Lifecycle) is structured, why the QA process runs as eight named stages, what the artifact ladder (MTP / FTP / STP / ATP / ATS / ATR / STR / RTP / RTR) means, where each invariant is enforced, and how THIS project adapts it. Load it whenever someone asks why the process is shaped this way, what a stage / step / phase / cycle / al…

  .agents/skills/iql-context/SKILL.md on GitHub (opens in a new tab)

• jira-administration

  Run bounded Jira administration workflows for project Components or Atlassian instance migration. Use for jira-components, sync Jira components, jira-instance-migration, changed Jira URL, or repoint Jira. Both modes are sealed behind read-first analysis and explicit user approval before any Jira, credential-session, or repository mutation.

  .agents/skills/jira-administration/SKILL.md on GitHub (opens in a new tab)

• judgment-day

  Trigger: judgment day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.

  .agents/skills/judgment-day/SKILL.md on GitHub (opens in a new tab)

• orca-orchestration

  Multi-session agent orchestration for this repo: one conductor session coordinating a fleet of persistent worker sessions (one per story, per module, per failure cluster) through the Orca runtime, plus the non-Orca fallback where the same launch lines are pasted by hand. Owns the HOW of fleet work — terminals, Runs, Tasks, dispatch, briefs, claims, board cards, liveness, cleanup — while each work…

  .agents/skills/orca-orchestration/SKILL.md on GitHub (opens in a new tab)

• pr-review-lead

  Acts as a QA Lead / QA Architect reviewing a pull request's test-automation work against this repo's KATA doctrine (or the target repo's own doctrine, if it has one) and general QA best practices — grounding every finding in a concrete doctrine citation or code location, never a guess. Use whenever the user wants to review, audit, or give feedback on a colleague's or a teammate's PR, whether it l…

  .agents/skills/pr-review-lead/SKILL.md on GitHub (opens in a new tab)

• project-context

  Generate or refresh the business context maps (the HTML maps inside business-data-context, business-api-context and business-e2e-context) and the master test plan. Use for business-data-map, business-api-map, business-e2e-map, business-feature-map, user journeys map, master-test-plan, refresh project context, refresh all context, entity map, feature inventory, API business map, or risk-ranked tes…

  .agents/skills/project-context/SKILL.md on GitHub (opens in a new tab)

• project-discovery

  Onboard a project through four discovery phases: Constitution, Architecture, Infrastructure, and Specification. Produces the domain map (business model + glossary) inside `business-domain-context` and the infra map (architecture, NFRs, backend, frontend, environments, CI/CD) inside `infra-context`, plus `.context/project-config.md` and a backlog connection check, then hands the business maps and…

  .agents/skills/project-discovery/SKILL.md on GitHub (opens in a new tab)

• regression-testing

  Execute regression test suites via CI/CD, analyze results, classify failures, and produce GO/NO-GO release decisions. Use when running regression, smoke, or sanity suites through GitHub Actions, monitoring workflow runs, downloading Allure or Playwright artifacts, classifying failures (REGRESSION vs FLAKY vs KNOWN vs ENVIRONMENT vs NEW TEST), computing pass-rate and trend metrics, deciding releas…

  .agents/skills/regression-testing/SKILL.md on GitHub (opens in a new tab)

• session-handoff

  Compact an entire agent session into a handoff document so a NEW session resumes exactly where this one stopped, as if the context window had been extended rather than reset. Use when the context window is getting high (default threshold ~500k tokens, beyond which the model degrades and starts inventing), when work must continue past the end of this session, or on any variant of: hagamos el hando…

  .agents/skills/session-handoff/SKILL.md on GitHub (opens in a new tab)

• shift-left-testing

  Orchestrates pre-sprint Shift-Left QA on a batch of backlog Stories. Use when the user wants to refine acceptance criteria, surface ambiguities + gaps, draft an ATP outline, and hand off to PO/Dev BEFORE the Story enters a sprint — so defects are prevented in the requirements, not detected after implementation. Triggers on: shift-left testing, shift-left these stories, groom the backlog, pre-spri…

  .agents/skills/shift-left-testing/SKILL.md on GitHub (opens in a new tab)

• sprint-conductor

  Boot, run and resume the sprint QA conductor: one session that conducts a fleet of sprint-testing workers (one per ticket) on Orca and watches the whole sprint from one fixed point, the Sprint Board. Boots in one pass (sprint and board, the conductor-owned pre-flight, the Run, the sentinel, what the owner and the workers left, one status screen), runs one watch pass per sentinel wake (tickets tha…

  .agents/skills/sprint-conductor/SKILL.md on GitHub (opens in a new tab)

• sprint-testing

  Orchestrates in-sprint manual QA per issue across Stages 1 (Planning), 2 (Execution) and 3 (Reporting). Use for user-story testing, bug retesting, and sprint-wide QA loops. Creates the PBI folder, drives session-start, runs the triage + veto + risk-score decision tree on bugs, produces the ATP + ATR + TC artifacts in the TMS, executes smoke and trifuerza (UI/API/DB) exploration, and files the fin…

  .agents/skills/sprint-testing/SKILL.md on GitHub (opens in a new tab)

• test-automation

  Plan, write, and review automated tests following KATA (Komponent Action Test Architecture) on Playwright + TypeScript, or explain existing automated tests in a sealed read-only mode. Use when writing E2E or API/integration tests, creating Page or Api components, designing ATCs, parameterizing test data, registering fixtures, reviewing test code for KATA compliance, or requesting break-down-tests…

  .agents/skills/test-automation/SKILL.md on GitHub (opens in a new tab)

• test-documentation

  Analyze, prioritize, and document test cases in TMS (Jira/Xray), repair an existing Story-ATS-ATP-ATR-TC cascade through a sealed explicit mode, or run the sealed post-promotion `merged` pass once automated tests land on the production branch. Use for Test/ATP/ATR artifacts, ROI and automation verdicts, maintaining traceability, fix-traceability, or broken TMS links. The repair-traceability mode…

  .agents/skills/test-documentation/SKILL.md on GitHub (opens in a new tab)

• test-framework-adaptation

  Adapt this boilerplate's KATA test architecture, auth, schemas, variables, env schema, fixtures, CI, MCPs, and reporting to a project already reverse-engineered by project-discovery. Use for adapt framework, adapt KATA, wire fixtures, connect boilerplate to target stack, wire auth, or test framework adaptation (formerly adapt-framework). Strict gate: analysis and plan first, explicit approval, th…

  .agents/skills/test-framework-adaptation/SKILL.md on GitHub (opens in a new tab)

• xray-cli

  Xray Cloud test management via `bun xray` CLI: create/list tests, manage test executions and plans, import JUnit/Cucumber/Xray JSON results, update run statuses, back up and restore projects, link defects. Triggers on: create a test in Xray, import test results to Xray, list Xray executions, update run status, backup Xray project, restore Xray tests, link defect to run, sync tests, Xray auth logi…

  .agents/skills/xray-cli/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• pstackby backnotprop Use pstack with claude, codex, pi - Skills and principles for rigorous AI-assisted engineering 3.7k stars · 30 skills
• agent-master-skillsby LeoYeAI 🧠 Curated collection of 2700+ best agent skills — AI, coding, marketing, design, finance and more. Harness-agnostic: works with Claude Code… 2.2k stars · 28 skills
• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 185k stars · 6 skills
• taste-skillby Leonxlnx Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages 111k stars · 1 skill
• archifyby tt-a1i Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more. 93.9k stars · 5 skills
• awesome-claude-skillsby ComposioHQ A curated list of awesome Claude Skills, resources, and tools for customizing Claude AI workflows 78.9k stars