linear-update-summary

Post structured development summaries to Linear issues with git context.

Updated Oct 15, 2025

Search Tags:#mcp #linear #diffs #uat #git-commits #update-summary

Ready to run

npx skills add https://github.com/kingler/v0-jetvision-assistant --skill linear-update-summary

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: linear-update-summary
Source: https://github.com/kingler/v0-jetvision-assistant/tree/main/.claude/skills/linear-update-summary
Command: npx skills add https://github.com/kingler/v0-jetvision-assistant --skill linear-update-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates posting structured development summaries to Linear issues, consolidating git context, file changes, and decision-making notes into a single, auditable update.

Core Features & Use Cases

Auto-gather git commits, file changes, and branch context to build a complete progress snapshot.
Assemble a structured Linear comment that includes an Activities Completed section, any Bug Fixes, and a Changes Summary, plus an interactive UAT checklist.
Post the summary to Linear via the MCP and present a review preview before posting to ensure accuracy.

Quick Start

Run the command /linear-update-summary ONEK-XXX on your feature branch to post a structured development summary to the Linear issue.

Frequently Asked Questions about linear-update-summary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I post a structured development summary to a Linear issue from git commits?▼

To post a structured development summary to a Linear issue, run the command on your feature branch to auto-gather git commits, file diffs, and branch context into a comprehensive update.

Can I generate a UAT checklist in Linear automatically from file diffs?▼

Yes, you can generate an interactive UAT checklist in Linear automatically by assembling file diffs and branch context into a structured comment that includes a changes summary and testing items.

Does the linear-update-summary workflow require a configured Linear MCP?▼

Yes, this workflow requires a configured Linear MCP to post the structured summary, a feature branch with commits since diverging from main, and the gh CLI to detect pull requests and attach context.

What is the best way to add a changes summary to Linear before UAT?▼

The best way to add a changes summary to Linear before UAT is to operate across pre-UAT scenarios, auto-gathering git context to build a comment with activities completed, bug fixes, and an interactive checklist.

How do I preview a Linear update before posting it via MCP?▼

You can preview a Linear update before posting it via MCP because the workflow assembles the structured comment and presents a review preview to ensure accuracy before the final submission.

Will this summary workflow work without a feature branch diverged from main?▼

No, this summary workflow will not work without a feature branch because it requires commits since diverging from main to gather the necessary git context and build a complete progress snapshot.