oss-guidelines

/oss-guidelines [repo]

Surface for the per-repo guidelines machinery (#867 / #1283). Most users land here after the extract-learnings workflow has run at least once and want to read, edit, or reset what was stored — without re-running the full extraction.

Inputs

• [repo] — optional. owner/repo shorthand. When omitted, this command lists every repo with stored guidelines and asks which one the user wants to operate on.

What it does

Bundle freshness: the steps below prefer the MCP tools (no bundle needed). If you fall back to a cli.bundle.cjs call, first ensure the bundle reflects the installed plugin version — the plugin ships no prebuilt bundle, so a stale one can persist after an update. Run "${CLAUDE_PLUGIN_ROOT}/scripts/build-cli-if-stale.sh" "${CLAUDE_PLUGIN_ROOT}" once before the first bundle call (exit 2 = build failed: stop and surface it). Skip this entirely when using the MCP tools.

1. Resolve the target repo.

   • If an argument was passed, use it verbatim.
   • Otherwise, enumerate repos with stored guidelines via the mcp__plugin_oss-autopilot_oss-autopilot__guidelines-list tool when the MCP server is available, or cli.bundle.cjs guidelines list --json otherwise. Both return { repos, count, storageMode }. Present the list via AskUserQuestion.
   • If no guidelines exist for any repo, surface a one-line nudge toward extract-learnings and exit.

2. Render the current guidelines.

   ## Guidelines for {owner}/{repo}
   Stored: {byteSize} bytes, last updated {timestamp}
   
   {markdown content}
   

   Read via mcp__plugin_oss-autopilot_oss-autopilot__guidelines-get when available; fall back to cli.bundle.cjs guidelines view --repo OWNER/REPO --json otherwise.

3. Offer follow-up actions. Use AskUserQuestion:

   • Re-extract from recent PRs — dispatches the extract-learnings.md workflow scoped to this repo.
   • Edit guidelines — invokes the edit-guidelines.md workflow (load → user edit → store, no extraction step).
   • Reset (delete) — calls cli.bundle.cjs guidelines reset --repo OWNER/REPO after a confirm prompt. Tombstones the entry in the gist (#867 semantics).
   • Done — exit cleanly.