Create /validate-ticket skill mirroring /review-ticket pattern #228

New issue

Closed

opened 2026-03-29 04:26:35 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-29 04:26:35 +00:00

Contributor

Type

Story (sub-ticket of #209)

Lineage

Parent: #209 (right-side validation pipeline)
Sub-ticket 3 of 3. Depends on #226 (docs must describe the validation flow before the skill references them).

Repo

forgejo_admin/claude-custom

User Story

As the platform operator
I want a /validate-ticket skill that executes production validation for board items in the validation column
So that validation follows a consistent, repeatable process with evidence captured in pal-e-docs

Context

The /review-ticket skill handles the left-side todo→next_up gate. This ticket creates its right-side mirror: /validate-ticket for the needs_approval→validation→done pipeline. The skill dispatches an agent that:

Parses the board item (board-slug#item-id)
Resolves the linked Forgejo issue and PR
Executes validation checks per template-validation
Creates a validation note in pal-e-docs
Reports PASS/PARTIAL/FAIL verdict
On PASS, moves the board item to done

The skill-validate-ticket note already exists in pal-e-docs (id: 841, active). The skill reads this note at execution time.

File Targets

Files to create:

~/.claude/skills/validate-ticket/SKILL.md — routing skill that dispatches validation agent. Must mirror ~/.claude/skills/review-ticket/SKILL.md structure.

Files to verify (already exist):

pal-e-docs note skill-validate-ticket (id: 841) — verify current and update if needed
pal-e-docs note template-validation — reference only, do not modify

Files to read (pattern reference):

~/.claude/skills/review-ticket/SKILL.md — the left-side skill to mirror

Files NOT to touch:

~/.claude/hooks/board-item-on-merge.sh — covered by #227
~/.claude/settings.json — skill registration is automatic via SKILL.md convention
Any pal-e-docs flow diagrams — covered by #226

Acceptance Criteria

~/.claude/skills/validate-ticket/SKILL.md exists and follows review-ticket SKILL.md pattern
Skill parses board item reference, resolves issue/PR, executes validation per template-validation, creates validation note, reports verdict
End-to-end: run /validate-ticket board-slug#item-id on an item in validation → validation note created, verdict reported, item moved to done on PASS

Test Expectations

Verify SKILL.md file exists at expected path
Read SKILL.md and verify it references skill-validate-ticket note and template-validation
Manual test: run /validate-ticket on a real board item in validation column
Run command: cat ~/.claude/skills/validate-ticket/SKILL.md

Dependencies

#226 must be complete first — the flow diagrams in sop-board-workflow and agent-workflow must describe the validation column before this skill references them
skill-validate-ticket note (id 841) must be current — verify at execution time

Constraints

Must mirror /review-ticket structure exactly (routing skill pattern)
template-validation defines the validation note format — the skill must follow it exactly
Skill dispatches a fresh-context agent (same pattern as review-ticket)
Agent: Dev (Devy)

Checklist

PR opened
Tests pass
No unrelated changes

#209 — parent issue (DECOMPOSED)
#226 — sibling + dependency: doc fixes (must complete first)
#227 — sibling: merge hook fix
#161 — left-side scope review pipeline (companion)
review-ticket skill — the left-side pattern to mirror
skill-validate-ticket — pal-e-docs note (id 841, pre-existing)
template-validation — validation note template
review-518-2026-03-28 — scope review

### Type Story (sub-ticket of #209) ### Lineage Parent: #209 (right-side validation pipeline) Sub-ticket 3 of 3. **Depends on #226** (docs must describe the validation flow before the skill references them). ### Repo `forgejo_admin/claude-custom` ### User Story As the platform operator I want a `/validate-ticket` skill that executes production validation for board items in the `validation` column So that validation follows a consistent, repeatable process with evidence captured in pal-e-docs ### Context The `/review-ticket` skill handles the left-side `todo→next_up` gate. This ticket creates its right-side mirror: `/validate-ticket` for the `needs_approval→validation→done` pipeline. The skill dispatches an agent that: 1. Parses the board item (board-slug#item-id) 2. Resolves the linked Forgejo issue and PR 3. Executes validation checks per `template-validation` 4. Creates a validation note in pal-e-docs 5. Reports PASS/PARTIAL/FAIL verdict 6. On PASS, moves the board item to `done` The `skill-validate-ticket` note already exists in pal-e-docs (id: 841, active). The skill reads this note at execution time. ### File Targets Files to create: - `~/.claude/skills/validate-ticket/SKILL.md` — routing skill that dispatches validation agent. Must mirror `~/.claude/skills/review-ticket/SKILL.md` structure. Files to verify (already exist): - pal-e-docs note `skill-validate-ticket` (id: 841) — verify current and update if needed - pal-e-docs note `template-validation` — reference only, do not modify Files to read (pattern reference): - `~/.claude/skills/review-ticket/SKILL.md` — the left-side skill to mirror Files NOT to touch: - `~/.claude/hooks/board-item-on-merge.sh` — covered by #227 - `~/.claude/settings.json` — skill registration is automatic via SKILL.md convention - Any pal-e-docs flow diagrams — covered by #226 ### Acceptance Criteria - [ ] `~/.claude/skills/validate-ticket/SKILL.md` exists and follows `review-ticket` SKILL.md pattern - [ ] Skill parses board item reference, resolves issue/PR, executes validation per `template-validation`, creates validation note, reports verdict - [ ] End-to-end: run `/validate-ticket board-slug#item-id` on an item in `validation` → validation note created, verdict reported, item moved to `done` on PASS ### Test Expectations - [ ] Verify SKILL.md file exists at expected path - [ ] Read SKILL.md and verify it references `skill-validate-ticket` note and `template-validation` - [ ] Manual test: run `/validate-ticket` on a real board item in `validation` column - Run command: `cat ~/.claude/skills/validate-ticket/SKILL.md` ### Dependencies - **#226 must be complete first** — the flow diagrams in `sop-board-workflow` and `agent-workflow` must describe the validation column before this skill references them - `skill-validate-ticket` note (id 841) must be current — verify at execution time ### Constraints - Must mirror `/review-ticket` structure exactly (routing skill pattern) - `template-validation` defines the validation note format — the skill must follow it exactly - Skill dispatches a fresh-context agent (same pattern as review-ticket) - Agent: Dev (Devy) ### Checklist - [ ] PR opened - [ ] Tests pass - [ ] No unrelated changes ### Related - #209 — parent issue (DECOMPOSED) - #226 — sibling + dependency: doc fixes (must complete first) - #227 — sibling: merge hook fix - #161 — left-side scope review pipeline (companion) - `review-ticket` skill — the left-side pattern to mirror - `skill-validate-ticket` — pal-e-docs note (id 841, pre-existing) - `template-validation` — validation note template - `review-518-2026-03-28` — scope review