Add necromancer label-command workflow for PR regression test hardening#31125
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
pelikhan
May 9, 2026 02:14
View session
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new agentic workflow, necromancer, triggered via label_command on pull requests to investigate regression context and (when possible) generate and push test-only hardening changes back to the PR branch.
Changes:
- Introduces
.github/workflows/necromancer.mddefining thenecromancerlabel-command workflow, tooling, safe-outputs constraints, and the agent’s required investigation/testing process. - Adds the compiled workflow artifact
.github/workflows/necromancer.lock.ymlcorresponding to the new markdown workflow.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/necromancer.md | Defines the new Codex-powered PR regression-test hardening workflow, including safe-outputs constraints and agent instructions. |
| .github/workflows/necromancer.lock.yml | Compiled lock file for the necromancer workflow (generated artifact consumed by GitHub Actions). |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/2 changed files
- Comments generated: 2
| - "git grep:*" | ||
| - "git log:*" | ||
| - "git show:*" | ||
| - "go test:*" |
Comment on lines
+45
to
+53
| push-to-pull-request-branch: | ||
| allowed-files: | ||
| - "**/*_test.go" | ||
| - "**/*.test.js" | ||
| - "**/*.test.cjs" | ||
| - "**/*.spec.js" | ||
| - "**/*.spec.ts" | ||
| - "**/*.spec.tsx" | ||
| - "**/*.snap" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New Feature
This change adds a Codex-powered agentic workflow,
necromancer, triggered bylabel_commandon pull requests. It is designed to investigate regression context (original issue + fix + existing tests), generate missing regression coverage, and push test-only updates to the PR branch.What does this feature do?
Workflow trigger and execution model
.github/workflows/necromancer.mdwithlabel_command: necromancerscoped to pull requests.engine: codex,strict: true, status comments, and read-only job permissions.Regression investigation flow
Automated regression test generation + branch update
push-to-pull-request-branchto publish generated tests directly to the PR branch.*_test.go,*.test.*,*.spec.*, snapshots).add-comment) or explicitnoopwhen no meaningful test delta is possible.Compiled workflow artifact
.github/workflows/necromancer.lock.yml.Why is this feature needed?
Merge-ready PRs often close the immediate bug but leave regression vectors under-tested. This workflow codifies a repeatable “bug lineage → fix analysis → coverage augmentation” pass so regressions are less likely to recur after merge.
Implementation details