luke-test

QA control plane for the Luke monorepo. Decides what deterministic evidence is sufficient to consider a change correct, across lint, typecheck, Node unit, real-browser component, Postgres integration and Playwright E2E — then assesses, writes or executes that evidence. Reports PASS / FAIL / SKIPPED / QA GAP with residual risk rather than a bare green tick. Use after implementing a feature or fixing a bug, before committing. Modes: /luke-test (assess, read-only) | write | verify. Scoping: default = diff vs merge-base. /luke-test write apps/api | --since <ref>

What does this entry provide?

luke-test is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # Luke QA Control Plane The question this skill answers is: > **What deterministic evidence is sufficient to consider this change correct?** Not "which tests sh. 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 luke-test 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: brail/luke
Repo updated: Oct 28, 2026

Install command

codex skill install brail/luke

Install method: codex

Review the upstream source before running this command.

GitHub project View SKILL.md

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.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.

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

# Luke QA Control Plane The question this skill answers is: > **What deterministic evidence is sufficient to consider this change correct?** Not "which tests should I write". Writi

Report an issue with this listing