Token导航 LogoToken导航TokenDH.com
中转站排行榜
研究检索external-servicegithub未标认证来源可访问clear审计提醒

ln-403-task-rework（ln 403 任务返工）

Agent Skill

ln-403-task-rework 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

总安装

6,551

周安装

265

GitHub Stars

437

下载量

2,056
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：ln-403-task-rework（ln 403 任务返工）
来源仓库：https://github.com/levnikolaevich/claude-code-skills
仓库路径：skills/ln-403-task-rework
安装命令：
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-403-task-rework
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异；本站展示可直接复制的安装命令，安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-403-task-rework

简介

用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 支持基于关键词、任务场景或来源线索进行信息检索与筛选。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装使用。
  • 安装前需确认权限范围、维护状态及是否涉及联网或文件操作。
  • ln-403-task-rework 属于研究检索类 Skill，可作为该场景下的辅助能力补充。

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. If shared/ is missing, fetch files via WebFetch from https://raw.githubusercontent.com/levnikolaevich/claude-code-skills/master/skills/{path}.

Task Rework Executor

Type: L3 Worker

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.

Hex-line acceleration (if available): Use outline(file_path) before reading large code files. Use read_file() for discovery and read_file(edit_ready=true, verbosity="full") before any edit that needs revision and checksums. After edits: edit_file(base_revision=rev) → verify(checksums). Use changes() to show what was fixed.

Inputs

Use read_file() and edit_file() as the primary path for code/config/script/test files during rework. Keep read_file() discovery-first by default; request edit_ready=true, verbosity="full" only when you are about to reuse its revision/checksum protocol. Built-in Read/Edit are fallback only when hex-line is unavailable.

InputRequiredSourceDescription
taskIdYesargs, parent Story, kanban, userTask to rework

Resolution: Task Resolution Chain. Status filter: To Rework

Task Storage Mode

MANDATORY READ: Load shared/references/environment_state_contract.md, shared/references/storage_mode_detection.md, and shared/references/input_resolution_pattern.md

Extract: task_provider = Task Management → Provider (linear | file).

AspectLinear ModeFile Mode
Load taskget_issue(task_id)Read("docs/tasks/epics/.../tasks/T{NNN}-*.md")
Load review notesLinear commentsReview section in task file or kanban
Update statussave_issue(id, state)Edit the **Status:** line in file

File Mode transitions: To Rework → In Progress → To Review

MANDATORY READ: Load shared/references/mcp_tool_preferences.md — ALWAYS use hex-line MCP for code files when available. No fallback to standard Read/Edit unless hex-line is down.

Workflow (concise)

  1. Resolve taskId: Run Task Resolution Chain per guide (status filter: [To Rework]).
  2. Load task: Read task (Linear: get_issue; File: Read task file), review notes, parent Story. 2b) Goal gate: MANDATORY READ: Load 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.
  3. Plan fixes: Map each comment to an action; confirm no new scope added.
  4. Implement: MANDATORY READ: Load 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.
  5. Quality: Run typecheck/lint (or project equivalents); ensure fixes reflect guides/manuals/ADRs/research.
  6. 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.
  7. 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.

Runtime Summary Artifact

MANDATORY READ: Load shared/references/coordinator_summary_contract.md, shared/references/worker_runtime_contract.md, shared/references/task_worker_runtime_contract.md

Shared contract:

  • emit summary_kind=task-status
  • standalone mode omits runId and summaryArtifactPath
  • managed mode passes both runId and exact summaryArtifactPath before the worker writes its validated summary

Monitor (2.1.98+): When verification commands expected >30s, use Monitor. Fallback: Bash(run_in_background=true).

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.
  • Runtime summary artifact written to the shared task-status location.

Reference Files

  • Environment state: shared/references/environment_state_contract.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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

27.76%
按下载量换算571

Gemini CLI

22.02%
按下载量换算453

Codex

15.24%
按下载量换算313

OpenCode

12.5%
按下载量换算257

Antigravity

7.71%
按下载量换算159

windsurf

3.19%
按下载量换算66

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API，使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果，不能写成本站确认安全。

来源信息

GitHub 仓库

github.com

/levnikolaevich/claude-code-skills

SKILL.md 来源

github.com

/levnikolaevich/claude-code-skills/tree/main/skills/ln-403-task-rework

skills-sh

skills.sh

/levnikolaevich/claude-code-skills/ln-403-task-rework

agentskills-to

agentskills.to

/levnikolaevich/claude-code-skills/ln-403-task-rework

继续浏览同类 Skills

更多研究检索 Skills（73,675）返回 Skills 目录

上一个 Skill

ln-402-task-reviewer（ln 402 任务审阅者）

ln-402-task-reviewer 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

下一个 Skill

ln-404-test-executor（ln 404 测试执行器）

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据，避免为了通过测试而改坏真实逻辑；涉及浏览器或外部服务时，应区分本地模拟、测试环境和生产环境。