sync-github-story
Installation
SKILL.md
sync-github-story
Purpose
One-way sync of a local story markdown file to GitHub Issues. Auto-detects create vs update from github_issue in frontmatter.
github_issue present? |
Action |
|---|---|
| Absent / null | Pre-flight dedup search by title, then Create (linked as sub-issue of parent epic) if no match. Writes github_issue back to file. |
| Present | Update existing GitHub issue (title, body, labels, milestone), reconcile open/closed state with frontmatter status. A Change Log row is written only if the status transitioned. |
Difference from sync-jira-story: GitHub Issues are markdown-native, so no ADF translation; auth/retry/rate-limit are handled by gh CLI; "status transitions" map to gh issue close / gh issue reopen, since GitHub only has open/closed. Labels carry the priority signal.
Inputs
STORY_FILE_PATH(required) — path to the local story markdown file.DOC_BRANCH(optional) — branch to pin the issue's## Documentlink to. When set (e.g.review-storyandfinalisepass a durable branch likedevelopso the link survives feature-branch deletion), it is used verbatim. When unset,doc-link-branch.jsresolves it: the current branch's upstream only when that branch names this story (its own branch, or its epic's integration branch), else the repo default branch, thendevelop.