Skip to content

Add missing YAML frontmatter to find-regression-risk SKILL.md #36799

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PureWeen merged 1 commit into from
Jul 30, 2026
+21 −4
Merged

Add missing YAML frontmatter to find-regression-risk SKILL.md #36799

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions .github/skills/find-regression-risk/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,21 @@
---
name: find-regression-risk
description: >-
Detects potential regression risks in a PR by cross-referencing lines the PR
REMOVES against lines ADDED by recent labeled bug-fix PRs (`i/regression`,
`t/bug`, `p/0`, `p/1`) touching the same files. Purely mechanical — no AI/LLM.
Emits a CLEAN / OVERLAP / REVERT verdict plus structured findings. Triggers on:
"does this PR revert a previous fix", "check PR for regression risk",
"find regression risks in PR", "is this change reverting a bug fix".
Do NOT use for: assessing ship-readiness of a release branch (use
release-readiness), investigating CI failures (use azdo-build-investigator),
or general code review (use code-review).
metadata:
author: dotnet-maui
version: "1.0"
compatibility: Requires PowerShell (pwsh), git, and GitHub CLI (gh) authenticated against the target repository.
---

# find-regression-risk

Detects potential regression risks in a PR by cross-referencing removed lines against lines added by recent labeled bug-fix PRs.
Expand Down
7 changes: 3 additions & 4 deletions .github/workflows/skill-validation.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -254,10 +254,9 @@ jobs:
# nonstandard filename with --eval-spec. This also SKIPS SKILL.md structural
# linting. We do NOT
# lint SKILL.md / *.agent.md here on purpose: vally's skill linter flags
# two PRE-EXISTING repo issues unrelated to this migration (try-fix
# SKILL.md exceeds the 500-line limit; find-regression-risk is missing
# name/description frontmatter) that would false-red this gate. Those are
# tracked as follow-ups in the PR description.
# a PRE-EXISTING repo issue unrelated to this migration (try-fix
# SKILL.md exceeds the 500-line limit) that would false-red this gate.
Comment on lines 254 to +258

@kubaflo kubaflo Jul 26, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed — long-lived repo documentation shouldn't point at a PR description, which becomes untraceable once this merges, and the "We do NOT" fragment does read as truncated. Making the comment self-contained (state the actual constraint and, if there's a follow-up, link a tracking issue rather than "the PR description") is the right call. Reasonable cleanup.

(This branch is being actively iterated in another worktree on my side, so I'm validating rather than pushing to avoid colliding with that in-progress work.)

# That is tracked as a follow-up in the PR description.
- name: Lint eval specs
id: check
shell: bash
Expand Down
Loading