skills.rest
dianlight
dianlightCOMMUNITY
Explore all skills by this author →
GitHub

close-task-work

Validate checklist completion and sync GitHub issue status for docs/tasks/*.md files.

8|1|Updated Dec 9, 2024
Search Tags:#automation#workflow#docs#task-management#github-issues#pr-summary#close-task
One-click install
npx skills add https://github.com/dianlight/srat --skill close-task-work
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: close-task-work
Source: https://github.com/dianlight/srat/tree/main/.github/skills/close-task-work
Command: npx skills add https://github.com/dianlight/srat --skill close-task-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close out completed docs/tasks/*.md tasks by validating checklist completion, syncing GitHub issue status/comments, and preparing optional PR summary notes.

Core Features & Use Cases

  • Validate exactly one task file by ID/filename and ensure all checklist items are complete.
  • Sync and update linked GitHub issues with status and comments, preparing closure notes when ready.
  • Generate an optional PR-ready completion summary and update related documentation.
  • Provide a final closure report back to the user with status and actions taken.

Quick Start

Provide the task identifier and optional publish mode to close the task and produce a PR-ready summary if requested.

Frequently Asked Questions about close-task-work

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

FAQPage Schema
How do I automatically close completed task markdown files and sync the status to GitHub issues?▼

To automatically close completed task markdown files, you validate checklist completion and sync GitHub issue status. This workflow updates linked issues with closure comments and prepares PR-ready summary notes for documentation maintenance.

What is the process for validating task checklist completion before closing a GitHub issue?▼

Task checklist validation involves identifying a specific docs/tasks/*.md file by ID and ensuring all checklist items are complete. The closure mechanism then proceeds to sync GitHub issue status only after verifying every required item is checked.

How do I generate a PR completion summary from a closed task document?▼

Generating a PR completion summary requires providing a task identifier and optional publish mode. The workflow extracts completed checklist data from the task markdown file and formats it into PR-ready closure notes for review preparation.

Can I update multiple GitHub issues simultaneously when closing a task file?▼

No, the task closure workflow validates exactly one task file by ID or filename at a time. It syncs status and comments for a single linked GitHub issue to ensure accurate tracking and prevent mismatched closure reports.

What happens if a task markdown file has incomplete checklist items during closure?▼

If checklist items are incomplete, the task closure validation fails and prevents the GitHub issue status sync. The workflow requires all checklist items within the docs/tasks/*.md file to be complete before proceeding with closure actions.

Do I need GitHub API access to automate task markdown file closure?▼

Yes, GitHub API access is required to sync issue status and post closure comments. The task closure workflow updates linked GitHub issues with status changes and prepares PR summary notes using GitHub integration.

Related Skills

Explore More Product & Management Skills→
intent-integrity-chainintent-integrity-chain
47

iikit-09-taskstoissues

Convert tasks from tasks.md into standardized GitHub issues.

Official
Intermediate
CygnusfearCygnusfear
5

create-pr

Create pull requests with linked issues and closing keywords.

Community
Basic
anhhung04anhhung04
1

github-triage

Automate task creation and status updates from GitHub issues via the API.

Community
Basic
NSEvteevNSEvteev
31

issue-modify

Update, close, or reopen GitHub Issues with SSOT-guided validation.

Community
Intermediate