SSO, RBAC & audit · Any model, your keys · No seat tax
The per-PR runbook: run the suite, deploy to the test environment, exercise the change through the edge, and post the result.
kortix marketplace install kortix-starter:pr-qa-skill# Read the known-issues ledger before touching any branch — edge cases that
# have bitten before, flows that are critical, flaky tests already on file.
cat memory/qa-known-issues.md 2>/dev/null || echo "(no known issues yet)"
# Discover every PR opened or pushed to since the last sweep.
gh pr list --repo {{target_repo}} --state open \
--json number,headRefOid,statusCheckRollup,updatedAt
headRefOid already carries a qa-agent
check in statusCheckRollup — don't re-run against a revision you've already
reported on. Work through what's left one PR at a time, each as its own
independent unit: a failure on one PR is a self-contained result and never
blocks or contaminates QA of the others in this sweep.gh pr view --repo {{target_repo}} <PR_NUMBER> --json headRefOid,statusCheckRollup
rm -rf /workspace/pr-<PR_NUMBER>
git clone --filter=blob:none https://github.com/{{target_repo}}.git /workspace/pr-<PR_NUMBER>
cd /workspace/pr-<PR_NUMBER>
gh pr checkout <PR_NUMBER>
<install command for the stack> # e.g. pnpm install --frozen-lockfile / npm ci / pip install -r requirements.txt
cd /workspace/pr-<PR_NUMBER>
<unit test command> 2>&1 | tee /tmp/qa-unit.log
<integration test command> 2>&1 | tee /tmp/qa-integration.log
<e2e test command> 2>&1 | tee /tmp/qa-e2e.log
qa-known-issues.md for
flows that have broken before and confirm this run actually exercised them.<deploy command, e.g. an internal deploy script / flyctl / vercel> \
--env test --ref <PR head SHA>
curl -sf https://<test-deploy-host>/<changed-path> -o /tmp/qa-response.json
curl -sI https://<edge-fronted-test-host>/<changed-path> # routing, headers, caching, redirects
| Result | Criteria |
|---|---|
| Pass | Suite green, deploy healthy, exercised behavior matches expectation, edge checks clean |
| Fail | Any suite failure, a failed or unhealthy deploy, exercised behavior wrong, or an edge-only regression |
| Flag as flaky | A test fails, then passes on an isolated re-run with no code change — report it as flaky with both runs' logs; don't just retry until it's green |
gh api repos/{{target_repo}}/statuses/<PR_head_SHA> \
-f state=<success|failure> -f context="qa-agent" -f description="<one-line result>"
gh pr comment --repo {{target_repo}} <PR_NUMBER> --body "<pass/fail summary>"
<teardown command for the ephemeral test deploy>
memory/qa-known-issues.md with the PR link and a one-line
description, then land it durably:git add memory/qa-known-issues.md
git commit -m "docs(qa): record edge case from PR #<PR_NUMBER>"
project.cr.open action — an edit that only lives in the sandbox never
survives on its own; only a landed change request does. Then move to the next
PR in this sweep's batch, if any, with a clean checkout (Step 1).The role-to-grant policy, extra-scrutiny cases, the approval handshake, and how an applied grant gets logged.
Get a complete picture of any company or person before outreach. This skill always works with web search, and gets significantly better with enrichment and CRM data.
Daily runbook for budget pacing, CPA/ROAS drift, underperformer detection, and anomaly flags across Google Ads and Meta Ads, plus how to rank and word optimization recommendations.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
Extract-and-match runbook for incoming vendor invoices: line-item extraction, PO/prior-invoice matching, duplicate + overcharge detection, and the ledger + approval hand-off.
Search, dedupe against the seen-mentions ledger, classify sentiment and notability, and post a digest with suggested response drafts — the daily brand-monitor runbook.