ln-403-task-rework
Fixes tasks in To Rework and returns them to To Review. Applies reviewer feedback only for the selected task.
- License 许可
- MIT
- 最近更新
- 2026-05-02
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- ln-403-task-rework
- license
- MIT
- description
- Fixes tasks in To Rework and returns them to To Review. Applies reviewer feedback only for the selected task.
02 资源文件 17
- 参考文档agents/analyzer.md10.1 KB
- 参考文档agents/comparator.md7.1 KB
- 参考文档agents/grader.md8.8 KB
- 资产文件assets/eval_review.html6.9 KB
- 脚本eval-viewer/generate_review.py16.0 KB
- 参考文档eval-viewer/viewer.html43.9 KB
- 许可证LICENSE.txt11.1 KB
- 参考文档references/schemas.md11.8 KB
- 脚本scripts/__init__.py—
- 脚本scripts/aggregate_benchmark.py14.0 KB
- 脚本scripts/generate_report.py12.5 KB
- 脚本scripts/improve_description.py10.9 KB
- 脚本scripts/package_skill.py4.1 KB
- 脚本scripts/quick_validate.py3.9 KB
- 脚本scripts/run_eval.py11.2 KB
- 脚本scripts/run_loop.py13.3 KB
- 脚本scripts/utils.py1.6 KB
03 SKILL.md 正文
Paths: File paths (
shared/,references/,../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.
Task Rework Executor
Executes rework for a single task marked To Rework and hands it back for review.
Purpose & Scope
- Load full task, reviewer comments, and parent Story; understand requested changes.
- Apply fixes per feedback, keep KISS/YAGNI, and align with guides/Technical Approach.
- Update only this task: To Rework -> In Progress -> To Review; no other tasks touched.
Inputs
| Input | Required | Source | Description |
|---|---|---|---|
taskId |
Yes | args, parent Story, kanban, user | Task to rework |
Resolution: Task Resolution Chain. Status filter: To Rework
Task Storage Mode
MANDATORY READ: Load shared/references/tools_config_guide.md, shared/references/storage_mode_detection.md, and shared/references/input_resolution_pattern.md
Extract: task_provider = Task Management → Provider (linear | file).
| Aspect | Linear Mode | File Mode |
|---|---|---|
| Load task | get_issue(task_id) |
Read("docs/tasks/epics/.../tasks/T{NNN}-*.md") |
| Load review notes | Linear comments | Review section in task file or kanban |
| Update status | save_issue(id, state) |
Edit the **Status:** line in file |
File Mode transitions: To Rework → In Progress → To Review
Workflow (concise)
- Resolve taskId: Run Task Resolution Chain per guide (status filter: [To Rework]).
- Load task: Read task (Linear: get_issue; File: Read task file), review notes, parent Story.
2b) Goal gate: MANDATORY READ:
shared/references/goal_articulation_gate.md— State REAL GOAL of this rework (what was actually broken, not "apply feedback"). Combine with 5 Whys (shared/references/problem_solving.md) to ensure root cause is articulated alongside the rework goal. NOT THE GOAL: a superficial patch that addresses the symptom, not the cause. - Plan fixes: Map each comment to an action; confirm no new scope added.
- Implement: MANDATORY READ:
shared/references/code_efficiency_criterion.md— Follow task plan/checkboxes; address config/hardcoded issues; update docs/tests noted in Affected Components and Existing Code Impact. Before handoff, verify 3 efficiency self-checks. - Quality: Run typecheck/lint (or project equivalents); ensure fixes reflect guides/manuals/ADRs/research.
- Root Cause Analysis: Ask "Why did the agent produce incorrect code?" Classify: missing context | wrong pattern | unclear AC | gap in docs/templates. If doc/template gap found → update the relevant file (guide, template, CLAUDE.md) to prevent recurrence.
- Handoff: Set task to To Review (Linear: update_issue; File: Edit status line); move it in kanban; add summary comment referencing resolved feedback + root cause classification.
Critical Rules
- Single-task only; never bulk update.
- Do not mark Done; only To Review (the reviewer decides Done).
- Keep language (EN/RU) consistent with task.
- No new tests/tasks created here; only update existing tests if impacted.
- Do NOT commit. Leave all changes uncommitted — the reviewer reviews and commits.
Definition of Done
- Task and review feedback fully read; actions mapped.
- Fixes applied; docs/tests updated as required.
- Quality checks passed (typecheck/lint or project standards).
- Root cause classified (missing context | wrong pattern | unclear AC | doc gap); doc/template updated if gap found.
- Status set to To Review; kanban updated; summary comment with fixed items + root cause.
Reference Files
- Tools config:
shared/references/tools_config_guide.md - Storage mode operations:
shared/references/storage_mode_detection.md - [MANDATORY] Problem-solving approach:
shared/references/problem_solving.md - Kanban format:
docs/tasks/kanban_board.md
Version: 3.0.0 Last Updated: 2025-12-23
04 同仓库更多 Skills
zarr-python
Chunked N-D arrays for cloud storage. Compressed arrays, parallel I/O, S3/GCS integration, NumPy/Dask/Xarray compatible, for large-scale scientific computing pipelines.
zabbix
Zabbix monitoring system automation via API and Python. Use when: (1) Managing hosts, templates, items, triggers, or host groups, (2) Automating monitoring configuration, (3) Sending data via Zabbix trapper/sender, (4) Querying historical data or events, (5) Bulk operations on Zabbix objects, (6) Maintenance window management, (7) User/permission management
x-twitter-growth
X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.
what-if-oracle
Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like "what if...", "what would happen if...", "what are the possibilities", "explore scenarios", "scenario analysis", "possibility space", "what could go wrong", "best case / worst case", "risk analysis", "contingency planning", "strategic options", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
venue-templates
Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.