Skip to content

feat(pr-workflow): add pr-validate skill — evidence-based PR validation#56

Draft
MajorLift wants to merge 8 commits into
mainfrom
jongsun/add/260626-pr-validate-skill
Draft

feat(pr-workflow): add pr-validate skill — evidence-based PR validation#56
MajorLift wants to merge 8 commits into
mainfrom
jongsun/add/260626-pr-validate-skill

Conversation

@MajorLift

Copy link
Copy Markdown

What

Adds a pr-validate skill to the pr-workflow domain: the evidence-orchestration / claim-matching layer for proving a PR's behavioral claim before review or merge.

Why

We have capture skills (testing/visual-testing, testing/performance-testing, pr-manual-testing) and readiness checks (pr-readiness-check), but nothing that decides what evidence a PR's specific claim needs and assembles it. pr-validate fills that gap and defers capture to the existing skills rather than duplicating them.

How it fits

  • Complements pr-readiness-check (presence of tests/guidelines) by proving the behavior is correct.
  • References, does not duplicate: visual-testing (mm CLI), performance-testing, pr-manual-testing, pr-description.
  • Describes the MetaMask Autonomous Engineering Platform (visual_validation / perf_validation) as an autonomous evidence engine at the capability level.
  • Core principle: match evidence to the falsifiable claim; vacuous-pass discipline (non-empty evidence bundle); publish before/after into the PR template's Screenshots/Recordings section.

Files

  • domains/pr-workflow/skills/pr-validate/skill.md
  • domains/pr-workflow/skills/pr-validate/repos/metamask-extension.md

Opened as draft for maintainer feedback on domain placement (pr-workflow vs testing) and scope of the AEP section.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant