pal-e-docs

Skill: Validate Ticket

skill-validate-ticket Skill

active skill
Project

Skill: Validate Ticket

Post-merge validation agent workflow. Reads a ticket's acceptance criteria, executes verification against live systems, and creates a structured validation note with evidence.

Inputs

You receive from the router:
  • Board item metadata — title, item_type, labels, board_slug
  • Forgejo issue URL — the ticket spec with acceptance criteria
  • Merge context — which PR was merged, which repo

Steps

  • Step 0: Determine validation tier — Inspect ticket labels and scope to determine which tiers apply:
  • Read the Forgejo issue — Extract acceptance criteria from the issue body. Each AC becomes a validation check.
  • Identify the validation type — Based on ticket type and labels:
  • Execute each check — Run the applicable tier checks for each acceptance criterion:
  • Check for regressions — Verify nothing that was working before is now broken:
  • Create the validation note — mcp__pal-e-docs__create_note with:
  • Post Forgejo comment — Summary on the Forgejo issue: 
    ## Validation: {VERDICT}
Tiers executed: {tier_list}
Validation note: `validation-{issue-number}-{date}`
{Check count}: {pass_count} PASS, {fail_count} FAIL
{If FAIL: bullet list of failures}
  • Report verdict — Return verdict to caller. If PASS, ticket can move to done. If FAIL, create follow-up issue for the regression.

Validation Note Format

Tier Reference

Tier Environment What to check Tools
Tier 1 Local Pull main, run integration tests, build checks pytest, tofu plan -lock=false, svelte-check
Tier 2 Staging Deployment healthy, pods running, no error spikes kubectl (staging context), curl staging URLs
Tier 3 Production Live pod status, endpoint responses, UI screenshots kubectl, curl, browser screenshots, pal-e-docs MCP
Full tier definitions and escalation rules live in convention-validation-pipeline. That convention is the authoritative source for tier semantics; this skill implements them.
  • template-validation — the template this skill produces
  • skill-review-ticket — the left-side gate (scoping). This skill is the right-side gate (validation).
  • convention-validation-checkpoints — the three verification loops
  • convention-validation-pipeline — authoritative tier definitions (Tier 1/2/3) and escalation rules
  • sop-board-workflow — column semantics