software-qa

Plugin software-qa from marketplace modootoday in modootoday/marketplace. Commands read from the repo's manifest — 23 days ago.

Skills (9)

• code-change-review-verification

  Verify each finding of an AI or human code review against the diff and the code that would run, mark it confirmed, refuted or unverified with the call path or test that settles it, and list the docs, config keys and examples the diff made wrong with both lines quoted. Use when a review lists claimed

• defect-triage-evidence

  Decide whether a failing regression test is flaky or a product defect, and write the investigation note with confirmed facts apart from hypotheses - separate the symptom, the required behavior and the current behavior, collect rerun evidence, and label a cause as a hypothesis until it is reproduced.

• merge-conflict-dual-intent-check

  Resolve a git merge or rebase conflict so both sides' intent survives - state each side's intent in one sentence from its commit message and diff, write a resolution that keeps both, list the cases where both cannot hold instead of choosing silently, confirm no conflict markers remain and the names

• oss-issue-pr-triage

  Triage a maintainer's backlog with evidence - decide whether an old issue is still open by checking linked pull requests, later commits and a reproduction on the current version, propose a duplicate only when symptom, trigger and root cause match, and review a pull request against the issue it claim

• perf-experiment-loop

  Run or judge a profile, change and benchmark loop - name the bottleneck from a profile with numbers, change one thing per experiment against a stored baseline in the same environment, require the tests to pass and several repeats, report variance and regressions elsewhere, and reject a gain that sit

• published-cli-quickstart-verification

  Verify that CLI onboarding commands identify the available package, version and executable without workspace or PATH masking. Use when reviewing a public CLI quickstart, a scoped package has a different binary name, or local success may not reproduce for users. Not for publishing releases, upgrading

• qa-change-test-mapping

  Update test cases or a test strategy after a story, design or code change - build a requirement to change to case trace table, list changed behaviors with no case and cases with no behavior, flag duplicates, and propose manual versus automated per case for QA approval. Use when a story, diff or desi

• starter-template-freshness-smoke

  Check whether a reused project starter or boilerplate is still sound - list the dependencies each feature adds so unneeded ones can be cut, compare declared versions and the lockfile with the target runtime and the current support policy fetched at run time, generate in a clean directory then instal

• test-fixture-and-mock-build

  Build test support that stays honest - an API mock written from the API definition with its error statuses, pagination and latency, a fixture that takes and releases a port and proves recovery, and a test-runtime speedup that keeps every assertion and reports time before and after. Use when a develo