swe-implementer

Implement a software subtask on a dedicated branch with context7 research, tests, and linting.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/diegocanepa/agent-skills --skill swe-implementer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swe-implementer
Source: https://github.com/diegocanepa/agent-skills/tree/main/skills/swe-implementer
Command: npx skills add https://github.com/diegocanepa/agent-skills --skill swe-implementer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the implementation of a single, defined subtask within a larger software development project, ensuring code quality and adherence to project standards.

Core Features & Use Cases

  • Subtask Implementation: Focuses on completing one specific, granular task.
  • Branch Management: Creates and works within a dedicated feature branch for isolation.
  • Contextual Research: Leverages external documentation (via context7 MCP) before coding to ensure best practices and current API usage.
  • Validation: Includes linting and testing to ensure code quality before committing.
  • Use Case: An orchestrator skill breaks down a feature into multiple subtasks. The swe-implementer skill takes one of these subtasks, researches necessary information, writes the code and tests, validates them, and commits the changes to a new branch, preparing it for review.

Quick Start

Implement the current subtask by researching in context7, coding, testing, and committing to a new feature branch.

Frequently Asked Questions about swe-implementer

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

FAQPage Schema
How do I implement a single development subtask in an isolated git branch?

Subtask implementation involves creating a dedicated git branch, researching current documentation via context7, writing code and tests, validating with linting and unit tests, and committing the changes for review.

What is the best way to ensure code quality when completing a coding subtask?

The best way to ensure code quality when completing a coding subtask is to validate your work with linting and unit tests before committing the changes to the dedicated branch.

How does context7 documentation research integrate into the development workflow?

Context7 research integrates into the development workflow by querying external documentation before coding to ensure best practices and current API usage are applied to the subtask implementation.

Do I need an orchestrator to break down features before using this implementation approach?

An orchestrator is not strictly required, but this implementation approach is designed to handle a single, defined subtask that an orchestrator skill has broken down from a larger software feature.

Can I commit multiple features at once using this subtask implementation process?

You cannot commit multiple features at once, as this subtask implementation process focuses strictly on completing one specific, granular task within a dedicated branch to ensure isolation and code quality.

Why should I create a dedicated branch for a single coding subtask?

You should create a dedicated branch for a single coding subtask to isolate your changes, ensure adherence to coding standards, and prepare the validated code cleanly for review before merging.