repo-sync-steward
Sync workflow between the FrankX main repo and frankx.ai-vercel-website branches. Use when cherry-picking blog/content/code changes across repos, updating slugs/RSS, and preserving site integrity.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Repo Sync Steward
Scope
Keep the website repo aligned with the main FrankX content and site code without dragging in local tooling or internal docs.
Workflow
- Fetch and inspect targets
- Confirm remotes:
origin(FrankX) andvercel-website(site repo). - Fetch the target branch before syncing.
- Prepare clean source commits
- Stage only website-relevant paths:
-
content/blog/** -
public/rss.xml -
lib/**andapp/**links that reference blog slugs -
next.config.jsredirects (if slugs changed)
-
- Avoid:
.claude/,.tina/,.shared/,docs/,notes.md,task_plan.md.
- Apply to target safely
- Use a worktree for
vercel-website/<branch>to avoid dirty state. - Cherry-pick the prepared commits; resolve conflicts minimally.
- Validate
- Run
node scripts/validate-blog-frontmatter.jsif available. - Regenerate RSS with
node scripts/generate_feed.mjs. - Scan for old slugs:
rg -n "/blog/0[0-9]-"and ensure redirects exist.
- Push + record
- Push to
vercel-website/<branch>. - Log what was synced (commit IDs + key files) in a brief note.
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!