Compile Annual SRED Work Summary from GitHub, Notion & Linear

Collects a full year's worth of a person's GitHub PRs, Notion documents, and Linear tickets, groups them into projects, and writes the result into a single private Notion document as the upstream input for SRED project documentation. The time window is fixed to February 1 of the previous year through January 31 of the current year, determined from the actual system date rather than assumed. It gathers from the user: their GitHub username, which GitHub repositories to search (a comma-separated list, or a directory it scans for .git folders), whether to include incident documents, and any other users who might have authored relevant Notion documents. It then pulls, for the given window: GitHub PRs opened by that username in the specified repositories (via GitHub MCP or the gh CLI), Notion documents the user created (via Notion MCP), and Linear tickets assigned to the user (via Linear MCP) - filtering out anything tagged INC-X or INC-XXXX if incidents were excluded. Every link found is placed in the Notion document with no truncation or "...and N more" shorteners, then grouped into projects using the PR title and description, the full Notion document content, and the ticket title and description as grouping signals, following a fixed template with per-project PR, Notion-doc, and Linear-ticket counts and links with their dates. It also searches other named users' Notion documents for anything relevant to an existing project and folds those links in too, before returning the finished document's link.

Use it when a year's worth of PRs, Notion docs, and Linear tickets needs collecting into project groupings for SRED preparation, or as the upstream step before writing individual SRED project descriptions with a companion project-organizer skill - it needs a repeatable collection workflow across GitHub, Notion, and Linear for a fixed time window. GitHub, Notion, and Linear must be reachable before starting - Notion and Linear connected via MCP, GitHub via MCP or the gh CLI - and access should be requested from the user rather than assumed if any is missing. If a "SRED Work Summary [year]" document already exists, the skill stops and asks the user to rename the existing one rather than overwriting it, and all listed GitHub repositories must belong to the getsentry GitHub organization.

Input is a GitHub username, a repository list or directory to scan (via find . -maxdepth 2 -name ".git" -type d), an include/exclude-incidents decision, and any other users to cross-reference. Output is a private Notion document, "SRED Work Summary [year]", structured as:

### Projects

### [Project Name]
*Summary*: [X] PRs, [X] Notion docs, [X] Linear tickets

### Pull Requests [X]
*[repository name]
[Links to all the PRs]
- [link] - [Merge date]

### Notion Docs [X]
[Links to all the Notion docs]
- [link] - [Creation date]

### Linear Tickets [X]
- [link] - [Creation date]

with every PR, Notion doc, and Linear ticket link included in full and assigned to a project, plus a link back to the document itself returned to the user.

Pulls from GitHub (via MCP or the gh CLI), Notion (via MCP, both for reading source documents and writing the output document), and Linear (via MCP) for tickets, cross-referencing all three by title, description, and creation or merge dates within the fixed one-year window.

Engineers or managers preparing SR&ED tax-credit documentation who need a complete, grouped inventory of a year's GitHub, Notion, and Linear activity assembled automatically before writing individual project summaries.