skills/sync-skills/SKILL.md
Sync modified skills and agents back to the repo and create a PR. Use when user types /sync-skills or wants to save in-session skill improvements.
npx skillsauth add jamesc/skills sync-skillsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Sync any skills or agents that were modified during this session back to the source repository and create a PR with the changes.
Locate the skills repo: Find the cloned skills repo at .claude/skills-repo:
ls -la .claude/skills-repo/
If it doesn't exist, inform the user and suggest running scripts/init.sh first.
Detect changes: Compare installed skills/agents against the repo source:
diff -rq .claude/commands/ .claude/skills-repo/skills/ --exclude='.gitkeep' 2>/dev/null
diff -rq .claude/agents/ .claude/skills-repo/agents/ --exclude='.gitkeep' 2>/dev/null
If no differences found, inform the user that all installed skills/agents match the repo and stop.
Run the sync script (if available):
bash "$CLAUDE_PROJECT_DIR/scripts/sync-skills.sh"
If the script doesn't exist, perform manual sync:
ghReport results:
gh CLI), suggest manual steps:
cd .claude/skills-repo
git checkout -b sync/skill-updates
git add -A && git commit -m "chore: sync skill updates from project"
git push -u origin HEAD
gh pr create --title "chore: sync skill updates" --body "Synced from project session"
Verify: Confirm the PR was created and the changes look correct:
gh pr view --json url,title,state
tools
Find the next logical piece of work. Use when user types /whats-next or asks what they should work on next, or wants recommendations for the next task.
development
Use when navigating code, finding references, looking up definitions, understanding types, or tracing call hierarchies in TypeScript, Rust, or Beamtalk (.bt) files. Prefer LSP over Grep/Glob for any navigation task where symbol semantics matter.
data-ai
Find and update Linear issues that need labels, blocking relationships, or metadata. Use when user says '/update-issues' with criteria like 'no labels', 'missing agent-ready', 'needs size', etc.
development
Review current branch changes vs main. Use when user types /review-code or asks for a code review of their changes.