close

Close tracker tasks after validating and normalizing IDs with user confirmation.

Updated Dec 6, 2025

Search Tags:#audit #confirmation #close #task-id #tracker #id-normalization

Ready to run

npx skills add https://github.com/arttttt/CMIDCABot --skill close

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: close
Source: https://github.com/arttttt/CMIDCABot/tree/main/.codex/skills/close
Command: npx skills add https://github.com/arttttt/CMIDCABot --skill close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams effectively finalize tracker tasks by ensuring the correct task ID is targeted and a user confirmation is obtained before closure.

Core Features & Use Cases

ID normalization: automatically prefixes IDs with DCATgBot- when missing, ensuring consistent task references.
Confirmation workflow: requires explicit user consent before closing a task to prevent accidental removals.
Audit-friendly reporting: outputs a final "Task closed: <full_id>" message for traceability.

Quick Start

Close a tracker task by providing its ID. When prompted, confirm the action to complete the closure.

Frequently Asked Questions about close

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

FAQPage Schema

How do I close a tracker task without accidentally terminating the wrong issue?▼

To close a tracker task safely, this workflow requires explicit user confirmation before executing the final closure operation. This confirmation step prevents accidental task removals and ensures the correct issue is targeted for audit-friendly reporting.

What happens if I submit a tracker task ID without the required prefix?▼

When you submit a tracker task ID missing its prefix, the system automatically applies ID normalization to append the required prefix. This ensures consistent task references and validates the input before attempting to close the tracker issue.

How does the tracker task closure process report its final status for audits?▼

The tracker task closure process reports its final status by outputting a specific audit-friendly message. After user confirmation and ID normalization, it generates a final report stating 'Task closed: <full_id>' to provide traceability for the completed action.

Can I automate closing tracker tasks, or does the confirmation step block automated scripts?▼

Closing tracker tasks requires an explicit user confirmation step to prevent accidental actions, which inherently blocks fully automated scripts. This safeguard ensures that a human operator validates the input ID and consents before the close operation finalizes.

What is the best way to finalize tracker tasks for team reporting?▼

The best way to finalize tracker tasks is to use a confirmation workflow that validates the input ID and normalizes the format. This approach safely closes the issue and outputs a traceable 'Task closed: <full_id>' message suitable for team audit reporting.