Validate PR flight deployments against head SHA and Loki signals.
npx skills add https://github.com/cogni-dao/cogni --skill validate-candidate
Please help me install this Agent Skill. Skill: validate-candidate Source: https://github.com/cogni-dao/cogni/tree/main/.claude/skills/validate-candidate Command: npx skills add https://github.com/cogni-dao/cogni --skill validate-candidate
Close the deploy_verified loop for a PR flighted to candidate-a. Review the PR, confirm the candidate-a build matches the PR head SHA, enumerate impacted surfaces (API routes, UI pages, graphs), exercise each against the real deployed URL using captured authed Playwright state + agent-api-validation patterns, query Loki for observability signals from the agent's own requests, then post an approve/fail scorecard + matrix as a PR comment. Use this skill whenever the user asks to "validate the candidate-a deploy", "prove this PR on candidate-a", "close the deploy_verified loop", runs "/validate-candidate" (with or without a PR number), or asks to manually E2E-test a flighted PR. Explicitly don't use for pre-merge CI checks or local dev testing — this skill runs after candidate-flight has already succeeded.
Invoke the skill on the target PR (e.g., /validate-candidate 1080) to run the end-to-end validation and post the resulting scorecard to the PR.
High-intent search queries and answers about installing and using this skill.
You can validate a PR flight deployment by automating end-to-end checks against the live candidate URL, querying Loki for observability data, and executing Playwright-driven tests to generate a pass/fail scorecard.
Closing the deploy_verified loop involves confirming the candidate build matches the PR head SHA, exercising impacted API and UI surfaces, and posting an approve or fail scorecard matrix directly as a PR comment.
Run end-to-end PR validation after a candidate-flight has already succeeded and the deployment is live, explicitly avoiding pre-merge CI checks or local development testing scenarios.
Yes, you need captured authentication state, authenticated gh CLI, Loki access, and a live deployed candidate URL per node to successfully execute Playwright checks and verify observability signals.
No, the PR validation process enforces zero-disk-artifact runs, ensuring the final scorecard and matrix are generated and posted without writing any files to the local disk.
Enumerating impacted surfaces involves analyzing the PR changes to identify affected API routes, UI pages, and graphs, then exercising them via Playwright and agent-api-validation patterns against the deployed URL.
kennyolofsson23-netizenInspect failing GitHub Actions checks and extract failure context from PR runs.
fvadicamoMerge GitHub Pull Requests after pre-merge checks and reviewer replies pass.
langflow-aiAutomates Playwright-based end-to-end testing for the Langflow UI.
cristianoliveiraRun linting, type checks, tests, and builds locally before merging a PR.
