qamap-pr-qa

QAMap PR QA

Use QAMap as a final local QA pass before presenting a pull request for human review.

Workflow

1. Detect the comparison base.

   • Prefer the target PR base branch when known.
   • Otherwise use origin/main, then origin/master, then the repository default branch.

2. Run QAMap from the repository root. Prefer an already installed local binary:

   pnpm exec qamap qa . --base <base> --head HEAD --format agent
   

   If QAMap is not installed, disclose that the next command downloads the pinned package from the npm registry and follow the host's network approval policy before running it:

   npm exec --yes --registry=https://registry.npmjs.org --package=@ivorycanvas/[email protected] -- qamap qa . --base <base> --head HEAD --format agent
   

   This one-off form runs outside the target repository's package-manager contract, so it does not invoke Corepack or add a packageManager field. QAMap's analysis does not upload source code or make another LLM call. The calling agent still uses its own model tokens to invoke the skill and interpret the compact result.

   Prefer the compact agent format because it carries the decision contract in a fraction of the tokens. Drop --format agent for concise human-readable text, or use --format markdown for the full trace report. The agent JSON is a versioned contract (schema: qamap.qa v1, additive-only): see docs/agent-format.md in the QAMap repository.

3. Read analysisScope before interpreting package-relative evidence or commands.

   • Read commandCwd as the command working-directory contract. workspace-root means run the command from the repository root; selected-package means run it from selectedPath. Older v1 payloads may omit the field; default to the workspace root instead of guessing.
   • automatic-package means the root command already reran analysis with the selected package's routes, scripts, fixtures, and runner settings. Its commands include the package path and use commandCwd: "workspace-root"; use the workspace-aware automation.draftCommand as printed.
   • explicit-package keeps package-local commands and uses commandCwd: "selected-package" with selectedPath.
   • repository-root means QAMap could not safely select one package. Review candidates and reason; do not silently choose a package for a cross-package or root-spanning change.
   • Use an explicit scoped pass only when a human wants to override that decision: