card-done

Automate PM card closure after PR merges across Asana, Shortcut, Linear, and Jira.

Updated May 8, 2026
One-click install
npx skills add https://github.com/fractionwork/pm-skills --skill card-done
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: card-done
Source: https://github.com/fractionwork/pm-skills/tree/main/skills/card-done
Command: npx skills add https://github.com/fractionwork/pm-skills --skill card-done

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Closes PM cards automatically after a merge to ensure consistent handoff, documentation, and cleanup of work context.

Core Features & Use Cases

  • Automatically verify PR status and move the active card to the appropriate section (DONE or RFT) after a merge.
  • Post a concise summary comment with PR details and testing notes, and clear local context to prevent stale work state.
  • Supports Asana, Shortcut, Linear, and Jira workflows, covering both dev-linked and manual closeouts and accommodating downstream QA flows.

Quick Start

Close the active PM card after a merge by reading context, checking PR status, moving to the correct section, and posting a summary.

Frequently Asked Questions about card-done

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

FAQPage Schema
How do I automatically close Jira or Asana cards after a pull request merge?

You can automatically close PM cards after a PR merge by validating the active card status, verifying the PR, and transitioning the card to the correct workflow state. This applies to Asana, Shortcut, Linear, and Jira.

Does this card closure automation support both manual and dev-linked closeouts?

Yes, the card closure automation supports both dev-linked and manual closeouts across Asana, Shortcut, Linear, and Jira. It validates the active PR status and accommodates downstream QA flows to ensure proper state transitions.

How does the automated card closure workflow handle safe state transitions?

Automated card closure enforces safe state transitions through a strict verification sequence: it moves the card to the correct section, verifies the transition, and then completes the process to ensure a robust end-to-end workflow.

What happens to local work context after a PM card is moved to DONE?

After moving a PM card to DONE or RFT, the workflow posts a concise summary comment with PR details and testing notes, then clears local context to prevent stale work state from interfering with future tasks.

Do I need REST or GraphQL API integration to automate moving Shortcut or Linear cards post-merge?

Yes, automating post-merge card transitions requires integration with your PM system's REST or GraphQL APIs. This API connection allows the workflow to validate active cards and enforce safe state transitions across platforms.

Why use automated card closure instead of manually moving PM cards after a merge?

Automated card closure ensures consistent handoff, documentation, and cleanup of work context after a merge. It prevents stale work state by validating PR status, posting summary comments, and moving cards to the correct section automatically.