Repository navigation
agents: restore missing rule frontmatter and refine CI/rule guidance - #4387
Merged
Merged
Conversation
Several agent rules lacked YAML trigger frontmatter, preventing agent discovery, while CI monitoring and merge skills alerted on expected `do not merge` gates and contended over background monitor locks. In addition, Starlark, Windows, and documentation rules omitted guidance on forwarding executable targets, matching `.exe` suffixes in CLI output, and cross-linking public aliases bidirectionally. Add `model_decision` frontmatter to the unindexed rule files, document executable forwarding, `.exe` output matching, and bidirectional alias cross-references, skip expected `blocks-do-not-merge` failures when the `do not merge` label is active, and hand off background CI monitors before launching the merge shepherd.
Collaborator
Author
|
AI Disclosure: This PR was prepared with AI assistance ( This is an automatically generated agent comment. |
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.
Several agent rules lacked YAML trigger frontmatter, preventing agent
discovery, while CI monitoring and merge workflows alerted on expected
merge-blocking label gates, woke parent conversations early during
failure analysis, and contended over monitor locks. Domain rules also
omitted guidance on executable target forwarding, Windows
.exeCLIoutput matching, and bidirectional alias cross-references.
Add
model_decisionfrontmatter to unindexed rules and document thoseStarlark, Windows, and documentation conventions. Update CI monitoring
and merge skills to ignore expected
blocks-do-not-mergefailures whenthe merge-blocking label is active, scope failure analyzer alerts to
the analyzer subagent, and release active CI monitor locks before
launching the merge shepherd.