developer

Implement code changes from specifications into tested patches.

Updated Dec 6, 2025
One-click install
npx skills add https://github.com/arttttt/CMIDCABot --skill developer-arttttt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer
Source: https://github.com/arttttt/CMIDCABot/tree/main/.gemini/skills/developer
Command: npx skills add https://github.com/arttttt/CMIDCABot --skill developer-arttttt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams translate vague requests into concrete, working code by enforcing adherence to project conventions and acceptance criteria.

Core Features & Use Cases

  • Translate feature requests and bug reports into executable code changes.
  • Ensure compliance with project conventions, typing, and asynchronous patterns.
  • Provide incremental, testable patches that can be reviewed and merged.

Quick Start

Provide the specification and the target repository context. The AI will propose a minimal, working patch that implements the requested change, along with tests or verification steps. Then you apply the patch to your codebase.

Frequently Asked Questions about developer

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

FAQPage Schema
How do I translate feature requests into working code changes?

To translate feature requests into working code, provide the specification and repository context to generate minimal, executable patches that follow project conventions and acceptance criteria.

Can I use this to implement bug fixes from reports with async await patterns?

Yes, you can implement bug fixes using async await patterns by providing the bug report; the system generates tested code changes that enforce asynchronous patterns and explicit typing across languages.

Does this code implementation skill support multiple frameworks and languages?

This code implementation skill supports translating specifications into working code across languages and frameworks by enforcing project conventions, typing, and modular design.

What is the best way to ensure no placeholders are introduced during spec translation?

To ensure no placeholders are introduced during spec translation, the system automatically enforces modular design and explicit types, delivering incremental, testable patches ready for review.

How to get incremental testable patches from software engineering specifications?

To get incremental testable patches from software engineering specifications, input the feature request and repository context to receive a working patch alongside tests or verification steps to apply.