QAMap PR QA
Esegue un passaggio QA locale zero-LLM su un diff di PR e sceglie il comando di validazione
Richiede configurazione
Cosa fa
Avvolge la QAMap CLI so that before a pull request goes up, the agent derives change intent, behaviour lifecycle, QA scenarios and the repository's validation command from commits and the diff, with no cloud o LLM call. Si attiva quando stai preparing, reviewing o finalising a PR, o ask what a change needs to prove before merge. Richiede npm e network access, since the skill fetches @ivorycanvas/qamap at run time.
Rapporto di test
La CLI è reale e veloce — 3.8 seconds on a two-file branch diff, no LLM call, and it correctly pulled the added test contract with its file:line, named the changed file and selected npm test as the validation command; running that command exposed a genuine regression the branch had introduced. What it does not do is find the bugs itself: reading the same nine-line diff unaided surfaced both the breaking change to the existing discount code and a hardcoded 2027 epoch that silently disables a promo, neither of which appeared anywhere in QAMap's scenarios. It degrades on size — pointed at a real 14-file, 1783-line commit range in its own repository it returned a single scenario with an empty assertions list and an empty PR checklist. Useful as a deterministic handoff format and an anti-hallucination contract (it insists an unrun command is never a pass), not as an extra pair of eyes.
Testato il: 2026-07-30 · Claude Code 2.x (agent harness)
Installazione
git clone https://github.com/IvoryCanvas/qamap.git mkdir -p ~/.claude/skills cd qamap && cp -r skills/qamap-pr-qa ~/.claude/skills/qamap-pr-qa
Comandi e prompt di esempio
/qamap-pr-qaEsegue un passaggio QA locale zero-LLM su un diff di PR e sceglie il comando di validazione
Gli skill si attivano con richieste in linguaggio naturale, senza comandi da ricordare. Dopo l'installazione, prompt come questi lo attivano (in inglese):
I'm about to open a PR, what should this change be tested for?Review my branch before I raise the pull request and list QA scenariosGenerate a QA checklist for the diff against main before I merge