task-fix

Task-Fix Skill

Fix issues in a task package identified by task-verify, following task-build rules and conventions.

Input Requirements

Before invoking this skill, provide:

1. Task Package Path: Directory containing the task package (problem/, evaluation/, environment/, metadata.json)
2. Paper Folder Path: Directory containing the original paper and prior processing results (needed for context)

The task package directory must contain:

• task_verify_result.json: Output from task-verify (the issues to fix)

The paper folder must contain:

• {paper_id}.pdf and {paper_id}.html: Original paper files
• preprocessed/: paper-preprocess output (text.md, links.json, figures/, tables/)
• filter_result.json: Combined output from paper-filter + data-check
• repositories/: Cloned repositories (reference only)

NOTE: The task package path and paper folder path may be the same directory (task-build often builds in-place).

Output

CRITICAL: This skill MUST output both items below, even if no fixes were applied:

1. Fixed task package: Modified files in the task package directory
2. Fix log: task_fix_log.txt written to the task package directory

Core Principles

1. Targeted Fixes, Not Rebuilds

This skill makes targeted, minimal fixes to resolve specific verification failures. It does NOT rebuild the task package from scratch — that is task-build's job. Each fix should change only what is necessary to resolve the identified issue.

2. Priority Order

Process issues in this order:

1. Failed checks — must be resolved (these cause overall_status: "failed")
2. Warnings — should be resolved where possible (non-critical but improve quality)

3. Fix Dependency Order

Within each priority level, fix in phase order since later fixes may depend on earlier ones:

• Phase 0 (file structure) → Phase 1 (consistency) → Phase 2 (information firewall) → Phase 3 (benchmark design) → Phase 4 (dynamic testing)