share-learning

# share-learning Promote a single learning to the team's shared knowledge repo (`darkroomengineering/team-knowledge`) — the "public corpus" tier of the knowledge system (see `docs/knowledge-system.md`). Local, personal knowledge stays in auto-memory; this skill is only for things another teammate's agent would benefit from knowing. ## When to use Use when a learning meets the shared-tier bar from `AGENTS.md` (Knowledge Routing): an architecture decision the team must follow, a library gotcha that affects everyone, a convention, an incident postmortem, or a reusable pattern. If it is a personal preference, local project state, or an external pointer, let auto-memory handle it instead — do NOT post it. ## Inputs Invoked as `/share-learning <kind> "<text>"` where `<kind>` is one of: `decision`, `convention`, `gotcha`, `incident`, `pattern`. If invoked without arguments, infer the most likely `kind` and a concise `text` from the recent conversation, then show the user what you intend to post and confirm before posting. Before starting, run `gh auth status` and confirm the authenticated account can read `darkroomengineering/team-knowledge` (or `$KNOWLEDGE_REPO`) with `gh api repos/${KNOWLEDGE_REPO:-darkroomengineering/team-knowledge} --jq .full_name`. Stop with the failed prerequisite if either check fails. Do not wait until the write step to surface missing authentication or repository access. ## Steps 1. **Resolve the repo.** Read `$KNOWLEDGE_REPO` from the environment;...