--- name: post-ticket-summary-15781b5a6917 description: >- Posts a structured implementation summary comment to a Linear issue — what was built, key decisions, reuse patterns, and how to test. Use after completing work on a ticket to document the implementation for the team. argument-hint: [--preview] [--minimal] disable-model-invocation: true allowed-tools: - AskUserQuestion - Bash - Read - Glob - Grep - mcp__claude_ai_Linear__get_issue - mcp__claude_ai_Linear__list_comments - mcp__claude_ai_Linear__create_comment - mcp__claude_ai_Linear__get_project metadata: trigger: "After completing work on a ticket to document the implementation for the team." tags: "linear, documentation, communication" --- # Post Ticket Summary Add a structured implementation summary comment to a Linear issue after completing work. ## Preferences _Read `~/.claude/skills/post-ticket-summary/preferences.md` using the Read tool. If not found, no preferences are set._ ## Context _On startup, use Bash to detect: current git branch, recent commits (`git log --oneline -20`), and repo name (`gh repo view --json nameWithOwner -q .nameWithOwner`). Skip any that fail._ ## Command routing Check `$ARGUMENTS`: - **`help`** → display help then stop - **`config`** → interactive setup then stop - **`reset`** → delete `~/.claude/skills/post-ticket-summary/preferences.md`, confirm, stop - **`--preview `** → show comment without posting then stop - **`--minimal `** → use minimal template - **anything else** → post summary ### Help ``` Post Summary — Document implementation on a Linear issue Usage: /post-ticket-summary Post full summary /post-ticket-summary --preview Show without posting /post-ticket-summary --minimal Short summary (skip architecture/reuse) /post-ticket-summary config Set template preferences /post-ticket-summary reset Clear preferences /post-ticket-summary help This help Examples: /post-ticket-summary AIS-810 /post-ticket-summary --preview AIS-810 /post-ticket-summary --minimal AIS-810 What it does: 1. Reads the Linear issue and codebase 2. Analyzes recent commits and changed files 3. Builds structured summary comment 4. Posts to the Linear issue Current preferences: (shown above under Preferences) ``` ### Config Use **`AskUserQuestion`**: **Q1** — "Default template?" (full (default), minimal) **Q2** — "Which sections to include?" (multiSelect: true) - Implementation summary - Key decisions / architecture - What was reused - How to test - Notes **Q3** — "Auto-detect issue from branch?" (Yes (default), No — always ask) Save to `~/.claude/skills/post-ticket-summary/preferences.md`. ## First-time detection If no preferences file exists, show: "First time using /post-ticket-summary? Run `/post-ticket-summary config` to customize template sections, or continue with full template." Then proceed. ## Steps ### 1. Resolve issue - If issue ID provided in `$ARGUMENTS`, use it - If no ID and auto-detect is on, extract from branch name (pattern: `user/ais-NNN-*`) - If still no ID, ask via `AskUserQuestion` Fetch the issue: title, description, project, status. ### 2. Check for existing summary Fetch comments on the issue. If an implementation summary comment already exists, ask: "An implementation summary already exists. Replace it, or skip?" ### 3. Gather implementation details **From the codebase:** - Recent commits on current branch (pre-injected) - Key files changed: `git diff main...HEAD --stat` (or appropriate base) - Read the main changed files to understand what was built **From project context:** - CLAUDE.md for conventions - README.md for project overview **Ask user** (optional — use `AskUserQuestion` with all optional): - Loom URL or recording link (or placeholder) - Live/staging URL for testing - Any additional context worth documenting If user says "skip", use placeholders. ### 4. Build comment **Full template:** ```markdown ## Implementation Summary {1-2 paragraphs: what was built and the product goal. Focus on business value.} ### What Was Reused | Component | Source | Adaptation | |-----------|--------|------------| | {component} | {origin} | {what changed} | --- ## How to Test **Branch:** `{branch}` **Live URL:** {url or N/A} ### Steps 1. {step} 2. {step} 3. {step} --- ## Features ### 1. {Feature Name} {2-3 sentences from user perspective. What they see, what they can do, business value.} ### 2. {Feature Name} {Same structure} --- ## Key Decisions | Decision | Rationale | |----------|-----------| | {decision} | {why} | --- ## Notes - {Additional context} ``` **Minimal template:** ```markdown ## Implementation Summary {1-2 paragraphs} ## How to Test **Branch:** `{branch}` 1. {step} 2. {step} ## Notes - {anything important} ``` Apply section toggles from preferences. ### Content guidelines - **Summary**: Lead with the problem, then what the implementation does. - **Features**: User perspective — what they see and do. No file paths. - **Key Decisions**: Focus on the "why" behind non-obvious choices. - **Reuse**: Show what was leveraged vs built new. ### 5. Post or preview If `--preview`: display the comment and stop. Otherwise: post via `create_comment`. ### 6. Report ``` Posted implementation summary to {issue-id}. Sections: {list of included sections} Next steps: 1. Record Loom and update the link 2. Add screenshots if relevant 3. Replace any [PLACEHOLDER] markers ``` ### 7. Learn If user removes sections consistently, update preferences. If user adds custom sections, note the pattern. --- Source attribution: mostafa-drz Original project: https://github.com/mostafa-drz/claude-skills/blob/e289cedeca6f9d9d2fdd26ab43abc7ab3141c2cb/code/post-ticket-summary/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2026 Mostafa Darehzereshki Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: mostafa-drz Original project: https://github.com/mostafa-drz/claude-skills/blob/e289cedeca6f9d9d2fdd26ab43abc7ab3141c2cb/code/post-ticket-summary/SKILL.md Attribution basis: Source repository record Fields of work: Product Management, Project & Program Management, Development & Engineering Roles: Product Manager, Project Manager, Backend Developer Specialties: Specialty not specified Tools: Linear Country applicability: Country not specified Classification basis: Source category, role and specialization labels Instruction SHA-256: f3d04ba302410c53588a61907d71896e89c790bb2d9af50336bcbc6a952982b3