ingest-githublisted

# ingest-github: GitHub-to-vault connector > **`{SKILL_DIR}`** = this skill's own folder (locally: the directory this SKILL.md lives in; a served brain substitutes the real absolute path before you read this). If a path does not resolve, name the missing file and stop — never guess another location. Ingests recent GitHub repository activity into the vault as markdown the graphify pipeline can read and the rest of the AI Brain Starter substrate (decision log, session-close cascade, hooks) can act on. This is the second connector in the ingest-* pattern. Adding the next external source means writing a new normalizer, not a new architecture. ## When to use - User says `/ingest-github <owner/repo>` (with or without `--days N`) - User asks to capture, sync, ingest, or pull a GitHub repository into the vault - User mentions wanting recent PRs, issues, or commits available to the knowledge graph Do NOT use for: - Opening pull requests or creating issues (use the GitHub MCP write tools or `gh` CLI directly) - One-off PR diff reads (use `gh pr view` or the GitHub MCP) - Non-GitHub sources (Slack, Notion, email get their own connectors) ## How it works 1. Parse the `<owner>/<repo>` argument, normalize to a slug (`owner-repo`) 2. Fetch merged PRs from the last N days (default 7) via the GitHub MCP `list_pull_requests` tool (state=closed, filter to merged) 3. Fetch issues from the last N days via `list_issues` (any state, since the date window) 4. Fetch commits from the last N da