task-review

Analyze Asana task metadata and comments to identify target repositories.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/EdgeApp/edge-dev-agents --skill task-review-edgeapp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-review
Source: https://github.com/EdgeApp/edge-dev-agents/tree/main/.cursor/skills/task-review
Command: npx skills add https://github.com/EdgeApp/edge-dev-agents --skill task-review-edgeapp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq.

What problem does it solve?

This skill eliminates the manual overhead of parsing complex Asana tasks, attachments, and subtasks, ensuring developers have a clear, actionable implementation plan before writing code.

Core Features & Use Cases

  • Context Synthesis: Automatically fetches and processes task descriptions, comments, and attachments including PDFs, ZIPs, and images.
  • Intelligent Scoping: Greps codebase handles to identify the correct target repository, preventing cross-repo confusion.
  • Use Case: When a project manager assigns a complex feature request in Asana, this skill analyzes the requirements, identifies the affected files across multiple repositories, and summarizes the implementation approach for the developer.

Quick Start

Invoke the task review skill by providing the full URL of the Asana task you wish to analyze.

Frequently Asked Questions about task-review

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

FAQPage Schema
How do I analyze Asana task context to determine the right repository for implementation?

Analyzing Asana task context involves fetching task metadata, comments, and attachments to identify affected codebases through pattern matching. This skill automates that process by extracting requirements and providing structured summaries for developers.

What's the best way to extract implementation requirements from complex Asana tasks?

Extracting implementation requirements from Asana tasks is best handled by automatically synthesizing task descriptions, comments, and attachments. This skill processes PDFs, ZIPs, and images to generate a clear, actionable implementation plan.

Do I need an ASANA_TOKEN to automate Asana task analysis?

Yes, automating Asana task analysis requires an active ASANA_TOKEN for secure API authentication. You also need the jq dependency installed to handle JSON processing during the context extraction workflow.

Can I identify affected codebases across multiple repositories from an Asana task?

Yes, you can identify affected codebases across multiple repositories by grepping codebase handles within the task context. This intelligent scoping prevents cross-repo confusion when a project manager assigns a complex feature request.

How does task context extraction handle different attachment formats in Asana?

Task context extraction handles different attachment formats by automatically fetching and processing supported files like PDFs, ZIPs, and images attached to Asana tasks. This ensures all relevant project context is synthesized into the final summary.

Are there limitations when using automation for repo scoping from Asana tasks?

Automation for repo scoping relies on pattern matching to identify target repositories, which may require accurate codebase handles within the task context. It is not suitable if the Asana task lacks clear technical references or attachment data.