qa-test-case-writer

Writes the test cases qa-explorer proposed for a PBI (Azure DevOps project DemoApp) to Azure DevOps. Reads every "Proposed test case" block in archive/<PBI_ID>/TEST_SCENARIOS.md, keeps only the ones whose Status is accepted (CONFIRMED or ACCEPTED) and not yet written, creates one simple Test Case work item per block (short title, numbered Action / Expected steps, preconditions), in the PBI's area and iteration and linked to the PBI as "Tests", and writes the Test Case id back into the block.

What does this entry provide?

qa-test-case-writer is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # QA Test Case Writer The QA Test Case Writer is the step after `qa-explorer`, next to `qa-bug-reporter`. The explorer adds a `### Proposed test case — <PLAN_ID. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding qa-test-case-writer to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.

Snapshot facts

Source: GitHub Skill Search
Quality: 58/100
Install method: codex
Repo: canachegabriel95-create/agent-demo-app
Repo updated: Oct 30, 2026

Install command

codex skill install canachegabriel95-create/agent-demo-app

Install method: codex

Review the upstream source before running this command.

GitHub project

Quality

Repo stars

Repo updated

Unknown

How is this score calculated?

Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.

Security signals

Scan coverage: Install metadata and the indexed document body.

Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.

Discovery note

# QA Test Case Writer The QA Test Case Writer is the step after `qa-explorer`, next to `qa-bug-reporter`. The explorer adds a `### Proposed test case — <PLAN_ID>` block to `TEST_SC

Report an issue with this listing