lms-front: Skill for Claude Code

GH Repo Config — resolve repo facts once, reuse forever

Two kinds of facts feed a GitHub workflow: those discoverable from the repo and API at runtime (discover fresh, never cache) and those that aren't — which project board, which Slack channel, who reviews (ask once, cache in the config file, never ask again). The bundled scripts/config.sh manages the cache; invoke it by this skill's own path, <skill-dir>/scripts/config.sh.

The config file

<repo-root>/.claude/gh-workflow.config.json — created on first use, committed or gitignored at the user's discretion (tell them where it is so they can choose). Example shape; every field is optional and repo-specific:

{
  "projectBoard": { "owner": "<github-org-or-user>", "number": 1 },
  "slackChannel": "#pr-review",
  "slackChannelId": "C0123456789",
  "defaultReviewer": { "name": "Alex", "slackId": "U0123456789" },
  "prTemplate": ".github/pull_request_template.md",
  "branchConvention": "<type>/<N>-<slug>",
  "stackSkills": ["vercel-react-best-practices", "vercel-composition-patterns"]
}

Key ownership — which skill consumes what:

Key	Consumer
projectBoard	gh-board
slackChannel, slackChannelId, defaultReviewer	ship-pr
prTemplate	ship-pr
branchConvention	work-issue (branching)
stackSkills	work-issue (Step 1 skill loading — chosen once per repo, empty array means "none")

config.sh commands:

config.sh path         Print the config file path (may not exist yet)
config.sh read         Print the JSON, or "{}" if none
config.sh get <jq>     One value, e.g. config.sh get .projectBoard.number
config.sh init         Create it if missing (auto-migrates a legacy
                       work-issue.config.json if one exists)

Rules:

• If the file already has a value, trust it — don't re-ask or re-detect. If the user says a saved value is wrong mid-run, update the file immediately.
• Batch the questions. When several values are missing, ask about them in one AskUserQuestion call up front, not one at a time deep into a run.
• Write back whatever was resolved (asked or inferred) with config.sh init + editing the JSON, and tell the user you saved it and where.
• Missing config is not an error. An unconfigured feature (no board, no Slack) means the consuming skill skips that feature and says so.