Qa Project Context
petrkindlmann/qa-skills/skills/qa-project-contextby petrkindlmannb3bb61bd268bMIT168 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 4 months ago
Create and fill .agents/qa-project-context.md with the project's tech stack, test frameworks, CI/CD pipeline, environments, quality goals, risk areas, team structure, and conventions. This is the one file every other QA skill reads first, so they skip redundant discovery and give context-aware advice. Use when: "set up QA context," "configure testing," "initialize project," first use of any QA skill. Not for: bootstrapping a brand-new project's QA end-to-end — use qa-start (which calls this skill as its first step). Related: qa-start, risk-based-testing, test-strategy, qa-metrics, playwright-automation.
Add to a SourceWeft workspace
- Open the skill in your dashboard and add it to a workspace.
- Enable it for the chats that should use it.
This skill is instructions only: it ships no scripts to execute.
Add to SourceWeftYou will be asked to sign in first, then taken straight to this skill.
Ask your agent to install it
Paste this prompt into Claude Code, Codex, Cursor or another agent that can run commands — or into SourceWeft chat. The agent reads this skill's install guide, shows you its source, license and scripts, and installs it with the SourceWeft CLI once you agree.
Read https://sourceweft.com/skills/gh-petrkindlmann-qa-skills-qa-project-context/install.md and install the skill it describes. Before installing, show me its source, license and whether it ships scripts, and wait for my OK. Ask me before changing anything else on my machine.Install it yourself from a terminal
For Claude Code, Codex, Cursor and other local agents. The SourceWeft CLI fetches the skill from its source repository at the commit scanned here, and verifies every file against the hashes recorded when the skill was scanned. If anything differs, nothing is written.
npx @sourceweft/cli skills install @petrkindlmann/qa-project-contextAdd --agent claude-code, codex, cursor or universal to choose which agent gets it (Claude Code by default).
Upstream installer — not verified by SourceWeft
The open-source skills installer fetches the same pinned commit, but does not check the files against the hashes SourceWeft recorded.
npx skills add https://github.com/petrkindlmann/qa-skills/tree/b3bb61bd268b147476252c6ed5a0440c87b97441/skills/qa-project-contextSource and attribution
Source:petrkindlmann/qa-skillsinskills/qa-project-contextat commitb3bb61b
License: MIT
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from petrkindlmann/qa-skills
Visual Testing
petrkindlmann
Guides visual regression testing with Playwright screenshots and hosted tools like Chromatic, Percy and Argos CI.
Unit Testing
petrkindlmann
Guides writing effective unit tests in Jest, Vitest and pytest, covering test doubles, coverage gating, snapshots, fake timers and mutation testing.
Test Suite Curation
petrkindlmann
Audit a whole regression suite and prune/restructure it with evidence: per-test coverage fingerprinting, AST near-duplicate clustering, CI-history mining for never-failing and flaky tests, prune decision rules (redundant/obsolete/low-value/keep), smoke/core/extended tiering by risk and defect-detection history, and a defensible "what we deleted and why" record. Deletion is destructive — quarantine and human sign-off are mandatory. Use when: "audit the test suite," "prune redundant tests," "find duplicate tests," "which tests can we delete," "restructure into smoke/core/extended," "is this test pulling its weight," "shrink the regression suite." Not for: Judging whether an individual test is WELL-WRITTEN (smells, assertions) — that is ai-qa-review. Healing one flaky test at runtime — that is test-reliability. Bulk selector regeneration after a UI refactor — that is selector-drift-recovery. Related: ai-qa-review, coverage-analysis, test-reliability, risk-based-testing, qa-project-context.
Test Strategy
petrkindlmann
Produce a multi-quarter QA strategy document. Covers scope, risk-based prioritization, test levels (unit/integration/E2E), pyramid analysis, entry/exit criteria, quality KPIs, tool selection rationale, CI scaling levers, and timeline planning. Output is an actionable strategy document, not a shelf document. Use when: "test strategy," "QA strategy doc," "testing approach," "QA roadmap," "multi-quarter QA direction." Not for: a single-sprint or single-release plan — use test-planning. Not for: identifying which areas carry the most risk — use risk-based-testing first. Related: risk-based-testing, qa-metrics, release-readiness, test-planning, test-reliability.
Test Planning
petrkindlmann
Builds a one-page sprint or release test plan with coverage mapping, effort estimation, prioritization, allocation, and scheduling.
Test Migration
petrkindlmann
Guides incremental test-suite migration between frameworks, such as Selenium, Cypress, or Jest to Playwright or Vitest, with parallel CI.
More in AI & Agents
Ppt Template Creator
anthropics
Turns a user's PowerPoint template into a reusable skill that generates branded presentations.
Skill Development
anthropics
Guides creation of Claude Code plugin skills, covering structure, descriptions, progressive disclosure and validation.
Plugin Structure
anthropics
Guides the structure, manifest, and component layout of Claude Code plugins.
Command Development
anthropics
Guides creation of Claude Code slash commands, covering structure, YAML frontmatter, arguments and plugin features.
Claude Md Improver
anthropics
Audits CLAUDE.md files in a repository, scores their quality, and applies approved targeted improvements.
Find Skills
vercel-labs
Guides discovery, quality checking and installation of agent skills via the npx skills CLI.