Skip to content

ci: add sync-skills workflow#1841

Open
ko3n1g wants to merge 4 commits intomainfrom
ko3n1g/ci/sync-skills
Open

ci: add sync-skills workflow#1841
ko3n1g wants to merge 4 commits intomainfrom
ko3n1g/ci/sync-skills

Conversation

@ko3n1g
Copy link
Copy Markdown
Contributor

@ko3n1g ko3n1g commented Apr 14, 2026

Summary

  • Adds sync-skills.yml workflow to keep skills/ in sync with agent directories via the _sync_skills.yml@v0.91.0 reusable workflow
  • Removes stale skills/.claude directory
  • Adds Git & PR conventions section to AGENTS.md so agents know to use type(scope)?: description format for commit messages and PR titles (prevents bracket-prefix anti-patterns like [ci] fix: …)

Test plan

  • CI passes
  • Skills sync correctly on next push to main

Signed-off-by: oliver könig <okoenig@nvidia.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: oliver könig <okoenig@nvidia.com>
@akoumpa
Copy link
Copy Markdown
Contributor

akoumpa commented Apr 16, 2026

Hi @ko3n1g , thanks for making this.

Initially, i used the .claude/skills so that claude would find them out of the box, however, this created problem, because people mount their skills on .claude/skills and then git was causing issues, thus reverted back to using skills/.

Do you know if this would introduce any similar conflict?

@ko3n1g
Copy link
Copy Markdown
Contributor Author

ko3n1g commented Apr 16, 2026

Hi @ko3n1g , thanks for making this.

Initially, i used the .claude/skills so that claude would find them out of the box, however, this created problem, because people mount their skills on .claude/skills and then git was causing issues, thus reverted back to using skills/.

Do you know if this would introduce any similar conflict?

Yeah I think that would still lead to issues. Perhaps we want to add these folders to .gitignore as a follow-up this PR. We need a single source of truth so that we can symlink it for other agents into read-only dirs

Agents had no guidance on commit/PR title format, leading to
non-semantic titles like `[ci] fix: …` instead of `fix(ci): …`.
The new section calls out the Conventional Commits format,
valid types, the 80-char limit, and the bracket-prefix anti-pattern.

Signed-off-by: oliver könig <okoenig@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants