Share repository skills across agents - #5013
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3aea6705f3
ℹ️ 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".
| skills_only = bool(paths) and all( | ||
| path.startswith((b".agents/skills/", b".claude/skills/")) | ||
| for path in paths |
There was a problem hiding this comment.
When a PR edits .agents/skills/release/scripts/changelog_entry.py or adds any other executable beneath these prefixes, every changed path still satisfies this test, so run-static.yml skips static_analysis and run-tests.yml skips all substantive test jobs. A syntax- or lint-breaking change to the existing release helper can therefore merge without the repository's mandatory static validation; restrict the exemption to skill documentation and compatibility symlinks, or explicitly exclude executable files.
AGENTS.md reference: AGENTS.md:L18-L24
Useful? React with 👍 / 👎.
Repository skills lived only in Claude’s discovery directory, leaving Codex to find them manually. Move the shared files to
.agents/skillsand retain Claude symlinks, with a small addition requiring issue triage to consult earlier issues, PRs, and maintainer decisions in git history.Skills-only PRs skip expensive test and static-analysis work while preserving required check names. Changes outside the skill directories, including this workflow change, still receive normal validation.