Skip to content

feat: On schema changes, push the JSON schema to claude-skills repo#1857

Open
adityathebe wants to merge 2 commits intomainfrom
feat/claude-skills-schema
Open

feat: On schema changes, push the JSON schema to claude-skills repo#1857
adityathebe wants to merge 2 commits intomainfrom
feat/claude-skills-schema

Conversation

@adityathebe
Copy link
Member

@adityathebe adityathebe commented Jan 13, 2026

Summary by CodeRabbit

  • Chores
    • Added automated workflow to synchronize configuration schema files to the code plugin repository. The workflow triggers when schema files are updated or can be manually activated.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 13, 2026

Warning

Rate limit exceeded

@adityathebe has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 9 minutes and 51 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 83c7e1d and 0e3084d.

📒 Files selected for processing (1)
  • .github/workflows/sync-claude-schemas.yml

Walkthrough

A new GitHub Actions workflow is added to automate syncing local config schema files into the claude-code-plugin repository. The workflow triggers on schema file changes or manual dispatch, performs repository checkouts, syncs files via rsync, and commits the changes.

Changes

Cohort / File(s) Summary
GitHub Actions Workflow
\.github/workflows/sync-claude-schemas\.yml
Adds automated workflow to sync config schema files to external repository with git auto-commit, triggered on config/schemas/config_*.schema.json changes or manual dispatch
🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: automating the pushing of JSON schemas to the claude-skills repository when schema files change.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/claude-skills-schema

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Fix all issues with AI agents
In @.github/workflows/sync-claude-schemas.yml:
- Around line 3-7: The push trigger currently watches
config/schemas/config_*.schema.json across all branches; restrict it to the main
branch by adding a branches filter under the push trigger (e.g., add "branches:"
with "- main" nested alongside "paths") so the workflow only runs for pushes to
main that modify those schema files.
- Around line 9-14: Add an explicit permissions block to the GitHub Actions
workflow (for the job named "sync") to avoid default token perms; update the
workflow to include a minimal permissions entry (e.g., permissions: contents:
read) at the job or top level so the Checkout config-db step (uses:
actions/checkout@...) only receives read access to repository contents and no
broader default permissions.
📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0ecc20e and 83c7e1d.

📒 Files selected for processing (1)
  • .github/workflows/sync-claude-schemas.yml
🧰 Additional context used
🪛 GitHub Check: CodeQL
.github/workflows/sync-claude-schemas.yml

[warning] 11-33: Workflow does not contain permissions
Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {{contents: read}}

⏰ Context from checks skipped due to timeout of 900000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: test
🔇 Additional comments (1)
.github/workflows/sync-claude-schemas.yml (1)

23-33: Sync and commit logic looks correct.

The rsync with --delete ensures the target directory mirrors the source exactly. The git-auto-commit-action will commit to the default branch of claude-code-plugin.

Consider adding branch parameter to explicitly target the main branch in the target repository for clarity, though the default behavior should work correctly.

Optional: explicit branch targeting
       - name: Push changes to claude-code-plugin
         uses: stefanzweifel/git-auto-commit-action@28e16e81777b558cc906c8750092100bbb34c5e3 # v7.0.0
         with:
           commit_message: "chore: sync config scraper schemas"
           repository: ./claude-code-plugin
+          branch: main

…rmissions

- Only trigger on main branch to prevent syncs from feature branches
- Add explicit permissions block (contents: read) following security best practices
- Add explicit branch parameter to git-auto-commit-action for clarity
@adityathebe adityathebe requested a review from moshloop January 16, 2026 14:24
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.

1 participant