Skill

Compile Annual SRED Work Summary from GitHub, Notion & Linear

Collect a year of GitHub PRs, Notion docs, and Linear tickets, group them into projects, and write a private Notion Work Summary.

Works with githubnotionlinear

69
Spark score
out of 100
Updated last month
Source checked Oct 8, 2026
Version 19.0.1

Add to Favorites

Why it matters

Automatically gather a full year of GitHub pull requests, Notion documents, and Linear tickets for a developer, intelligently group them into projects, and generate a comprehensive private Notion document for SRED tax credit preparation.

Outcomes

What it gets done

01

Extract all PRs, Notion docs, and Linear tickets from a specified time window with optional incident filtering

02

Create a private Notion document with standardized SRED Work Summary structure

03

Intelligently group all collected links into logical projects based on content analysis

04

Enrich project groupings with relevant documents from collaborating team members

Install

Add it to your toolbox

Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-sred-work-summary | bash

After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.

Reports

Agent outcome reports

No reports yet

Overview

Collects a year of GitHub PRs, Notion documents, and Linear tickets for a user, groups them into projects by content, and writes every link - untruncated - into a single private Notion Work Summary document for SR&ED preparation. Use it to build the upstream inventory before writing individual SR&ED project descriptions, across a fixed February-to-January time window spanning GitHub, Notion, and Linear.

What it does

SRED Work Summary collects a year of a person's GitHub PRs, Notion docs, and Linear tickets, groups them into projects, and writes the result into a single private Notion document - the upstream summary that individual SR&ED project descriptions get written from afterward. It confirms GitHub, Notion, and Linear access first (Notion and Linear via MCP; GitHub via MCP or the gh CLI), collects the GitHub username, the repositories to search (a list, or a directory scanned with find . -maxdepth 2 -name ".git" -type d, all of which must be in the getsentry GitHub organization), whether to include incident documents, and any other users whose Notion docs might be relevant. It then creates a private Notion document titled "SRED Work Summary [current year]" - stopping if one already exists rather than overwriting it - and searches the window from February 1 of the previous year through January 31 of the current year for PRs opened by the user, Notion docs the user created, and Linear tickets assigned to the user, excluding anything tagged INC-XXXX if incidents were declined.

When to use - and when NOT to

Use it to gather a year's worth of PRs, Notion docs, and Linear tickets into project groupings for SR&ED tax-credit preparation, or whenever a repeatable collection workflow is needed across GitHub, Notion, and Linear for a fixed time window before writing individual SR&ED project write-ups. It requires all three services to already be reachable and stops to ask for access if they are not, and it refuses to run again over an existing Work Summary document with the same name for the year.

Inputs and outputs

Input is a GitHub username, a repository list or directory, an incident-inclusion choice, and an optional list of other users. Output is a private Notion document with a link for every single matching PR, doc, and ticket - explicitly never truncated or summarized as "...and 75 more" - grouped into projects using PR titles/descriptions, full Notion document content, and ticket titles/descriptions as the grouping signal, in a fixed Markdown structure with a Pull Requests, Notion Docs, and Linear Tickets subsection per project, each entry dated. Other users' relevant Notion documents are folded into the matching project afterward. The final output is the link to the completed Work Summary document.

Integrations

GitHub (MCP or gh CLI), Notion (MCP), and Linear (MCP).

Who it's for

Engineers or engineering leads at an organization claiming SR&ED tax credits who need a complete, gap-free inventory of a year's work across three systems before someone writes the actual project descriptions, instead of manually hunting through GitHub, Notion, and Linear history by hand.

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.