chore: sync public export#6
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5aeba625b9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| @@ -0,0 +1,48 @@ | |||
| <!-- Generated by Kernel. Edit canonical source under .agent/ instead. --> | |||
There was a problem hiding this comment.
When Copilot discovers repository skills under .github/skills, SKILL.md is expected to expose its name and description in YAML frontmatter; the added skills instead start with the Kernel HTML header before the ---, so frontmatter-at-start parsers will treat the metadata as missing and the new skills will not be loadable. This affects every new .github/skills/*/SKILL.md; move the generated marker after the frontmatter or otherwise keep --- as the first line.
Useful? React with 👍 / 👎.
| @@ -0,0 +1,15 @@ | |||
| <!-- Generated by Kernel. Edit canonical source under .agent/ instead. --> | |||
There was a problem hiding this comment.
For .github/instructions/*.instructions.md files, Copilot expects an applyTo frontmatter block at the start of the file to know which paths the instructions apply to. These generated instruction files start with the Kernel HTML header and contain no applyTo, so the review/testing guidance is not applied in Copilot sessions; add frontmatter such as a repository-wide glob before the body/header.
Useful? React with 👍 / 👎.
1 participant
Generated from the private Kernel source allowlist sync workflow.
Verification run by this workflow: