complete

$npx mdskill add TheBushidoCollective/han/complete

Validates all checklist items before marking a ClickUp task as complete to ensure thorough task closure.

  • Helps users ensure tasks are fully verified before finalizing them in project management.
  • Integrates with ClickUp API to fetch tasks, update statuses, and add comments.
  • Decides based on user confirmation of each checklist item, proceeding only if all are validated.
  • Presents results with formatted checklists, completion summaries, and suggestions for incomplete items.

SKILL.md

.github/skills/completeView on GitHub ↗
---
name: complete
description: Mark a ClickUp task as complete after validating checklist
---

# complete

## Name

clickup:complete - Mark a ClickUp task as complete after validating checklist

## Synopsis

```
/complete [arguments]
```

## Description

Mark a ClickUp task as complete after validating checklist

## Implementation

Complete a ClickUp task by validating all checklist items and transitioning to Done.

**Usage**: `/complete #ABC123` or `/complete ABC123`

**Steps**:

1. Use `clickup_get_task` to fetch task details including checklists and comments
2. Display all checklist items
3. Ask user to confirm each item is complete
4. If all confirmed:
   - Use `clickup_add_comment` to add completion summary
   - Use `clickup_update_task_status` to transition to "complete" or "done"
5. If any not confirmed:
   - List incomplete items
   - Keep task in current status
   - Suggest next steps

**Display Format**:

```
✅ Completing #ABC123: {name}

📋 Checklist Validation:

Checklist: "Acceptance Criteria"
1. ✓ {item 1} - COMPLETE
2. ✓ {item 2} - COMPLETE
3. ✗ {item 3} - INCOMPLETE
4. ✓ {item 4} - COMPLETE

❌ Cannot complete: 1 item not checked
- {item 3}

Suggestion: Complete remaining checklist items before marking as Done.
```

Only transition to Done if ALL checklist items are validated.

More from TheBushidoCollective/han

SkillDescription
absinthe-resolversUse when implementing GraphQL resolvers with Absinthe. Covers resolver patterns, dataloader integration, batching, and error handling.
absinthe-schemaUse when designing GraphQL schemas with Absinthe. Covers type definitions, interfaces, unions, enums, and schema organization patterns.
absinthe-subscriptionsUse when implementing real-time GraphQL subscriptions with Absinthe. Covers Phoenix channels, PubSub, and subscription patterns.
act-docker-setupUse when configuring Docker environments for act, selecting runner images, managing container resources, or troubleshooting Docker-related issues with local GitHub Actions testing.
act-local-testingUse when testing GitHub Actions workflows locally with act. Covers act CLI usage, Docker configuration, debugging workflows, and troubleshooting common issues when running workflows on your local machine.
act-workflow-syntaxUse when creating or modifying GitHub Actions workflow files. Provides guidance on workflow syntax, triggers, jobs, steps, and expressions for creating valid GitHub Actions workflows that can be tested locally with act.
ameba-configurationUse when configuring Ameba rules and settings for Crystal projects including .ameba.yml setup, rule management, severity levels, and code quality enforcement.
ameba-custom-rulesUse when creating custom Ameba rules for Crystal code analysis including rule development, AST traversal, issue reporting, and rule testing.
ameba-integrationUse when integrating Ameba into development workflows including CI/CD pipelines, pre-commit hooks, GitHub Actions, and automated code review processes.
analyze-performanceAnalyze performance metrics and identify slow transactions in Sentry