implement

Automate code modification, test execution, and commits in an isolated subagent.

78|6|Updated May 19, 2026
One-click install
npx skills add https://github.com/liu5540/reasonix-skill-powers --skill implement-liu5540
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/liu5540/reasonix-skill-powers/tree/main/skills/implement
Command: npx skills add https://github.com/liu5540/reasonix-skill-powers --skill implement-liu5540

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

在隔离子代理中执行具体开发任务(修改代码、运行测试、提交变更)所需的协作和流程被自动化,从而提高效率与一致性。

Core Features & Use Cases

  • Context reading and task understanding: 理解任务描述并获取实现所需的背景信息。
  • Targeted code modification and validation: 精确修改代码并运行相关测试以验证实现。
  • Commitment and self-review: 提交变更并进行自我审查,确保质量与可追溯性。
  • Use Case: Parent 代理分配一个实现任务时,子代理独立完成实现、测试和提交,然后回报结果。

Quick Start

直接接收实现任务,读取任务描述、修改代码、运行测试、提交变更并返回实现摘要。

Frequently Asked Questions about implement

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

FAQPage Schema
How do I automate code modifications and test execution inside an isolated subagent?

Automating code modifications and test execution inside an isolated subagent requires a structured workflow that reads task context, applies targeted code edits, runs validation tests, and commits changes with a self-audit before reporting results back to the parent agent.

What is the read-edit-test-commit workflow for delegated implementation tasks?

The read-edit-test-commit workflow is a strict process for delegated implementation tasks where a subagent reads task descriptions, modifies code precisely, executes relevant tests for validation, and commits changes to ensure traceable results and quality assurance.

How to ensure traceable results when a parent agent delegates a coding task?

To ensure traceable results when a parent agent delegates a coding task, the subagent must strictly follow the read-edit-test-commit workflow, perform a proper self-audit of modifications, and return a detailed implementation summary upon completion.

Does subagent task implementation require dependency configuration before use?

Subagent task implementation operates without external dependency configuration, requiring only the delegation of a concrete task from a parent agent to initiate the end-to-end code editing, testing, and version control workflow.

What's the best way to handle version control and code editing in an isolated subagent?

The best way to handle version control and code editing in an isolated subagent is automating the end-to-end workflow, which integrates precise code modifications, test execution, and automated change commitment for consistent, traceable development.

When should I not use an isolated subagent for end-to-end implementation?

You should not use an isolated subagent for end-to-end implementation if the task lacks a concrete description or clear context, as the workflow relies on strict task delegation and background information reading to perform accurate code modifications.