post-ticket-summary

Post a structured implementation summary to Linear after ticket completion.

2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/mostafa-drz/claude-skills --skill post-ticket-summary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-ticket-summary
Source: https://github.com/mostafa-drz/claude-skills/tree/main/code/post-ticket-summary
Command: npx skills add https://github.com/mostafa-drz/claude-skills --skill post-ticket-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After completing work on a Linear ticket, this skill posts a structured implementation summary that documents what was built, why it was built, and how it was tested.

Core Features & Use Cases

  • Generates a structured implementation summary from code changes, recent commits, and project context.
  • Supports full and minimal templates, with sections toggled via preferences.
  • Posts directly to Linear or provides a preview, and saves user preferences for future use.

Quick Start

Run /post-ticket-summary <issue-id> to post a full implementation summary to the Linear issue.

Frequently Asked Questions about post-ticket-summary

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

FAQPage Schema
How do I post an implementation summary to Linear after completing a ticket?

You can post an implementation summary to Linear by running a command with the issue ID. The skill reads code changes and project context, builds a template-driven summary, and posts it directly via the Linear API.

Can I preview a Linear ticket summary before posting it to the issue?

Yes, you can preview a Linear ticket summary before posting. The skill provides an optional preview mode, allowing you to review the generated implementation documentation before it is posted directly to Linear.

What is included in an automated Linear ticket implementation summary?

An automated Linear implementation summary includes structured documentation of what was built, why it was built, and how it was tested. It generates this content from recent code changes, commits, and project context using template-driven sections.

How do I customize the template for posting Linear ticket summaries?

You can customize the template for Linear ticket summaries by toggling sections via preferences. The skill supports both full and minimal templates, and saves your preferences for future use to ensure consistent documentation.

Does the Linear ticket summary automation work without additional dependencies?

Yes, the Linear ticket summary automation works without additional dependencies. It operates independently to read code context, build the summary, and post via the Linear API, requiring no extra components to function.

Why use an automated summary for Linear tickets instead of manual documentation?

Automated Linear ticket summaries ensure consistent, shareable documentation of what was built. By generating structured summaries from code changes and commits, it reduces manual effort and standardizes implementation reporting across the team.