annotask-apply

Name: annotask-apply
Availability: InStock
Author: kurtstohrer

Apply pending Annotask design tasks to source code with MCP tooling.

3|Updated Mar 28, 2026

Search Tags:#workflow #mcp #tasks #code #apply #annotask #design-tasks

Ready to run

npx skills add https://github.com/kurtstohrer/annotask --skill annotask-apply

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: annotask-apply
Source: https://github.com/kurtstohrer/annotask/tree/main/skills/annotask-apply
Command: npx skills add https://github.com/kurtstohrer/annotask --skill annotask-apply

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the application of pending Annotask design tasks to the source code, reducing manual patching and preserving task traceability.

Core Features & Use Cases

Fetch pending tasks from the Annotask task store, apply edits or structural changes to the codebase, and mark results for review.
Lock tasks, execute changes deterministically, and provide concise resolutions to streamline review.
Leverage MCP tooling when available to obtain structured task data and minimize CLI friction while supporting multiple task types like annotation edits, style updates, and a11y fixes.

Quick Start

Apply the pending Annotask design tasks to the source code.

Frequently Asked Questions about annotask-apply

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

FAQPage Schema

How do I automate applying design tasks to source code?▼

You can automate design task application by fetching pending tasks, executing edits or structural changes deterministically, and marking results for review. This controlled workflow reduces manual patching while preserving task traceability across the codebase.

What are pending design tasks in a codebase workflow?▼

Pending design tasks are structured work items fetched from a task store, encompassing annotation edits, style updates, and a11y fixes. They represent code changes awaiting application, review, and final resolution.

Do I need MCP tooling to apply code changes from tasks?▼

MCP tooling is optional when applying code changes from tasks. It is leveraged when available to obtain structured task data and minimize CLI friction, but the workflow supports safe fallbacks and clear resolutions without it.

Can I lock tasks before applying changes to the codebase?▼

Yes, you can lock tasks before applying changes to the codebase. Locking tasks ensures edits execute deterministically and provides concise resolutions, which streamlines the subsequent code review process and prevents conflicting modifications.

What types of code edits can be applied through an automated task workflow?▼

Automated task workflows support multiple code edit types, specifically annotation edits, style updates, and a11y fixes. These changes are applied incrementally and controlled to ensure safe fallbacks and clear resolutions.

What happens if an automated task application fails during execution?▼

If an automated task application encounters issues, the workflow relies on safe fallbacks and clear resolutions. This ensures incremental edits or structural changes do not corrupt the codebase and results remain accurately marked for review.