skills.rest
g2i-ai
g2i-aiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

code

Implement production code changes from a provided spec.

51|2|Updated Apr 20, 2026
Search Tags:#workflow#development#spec-driven#refactor#code#lint#tests
One-click install
npx skills add https://github.com/g2i-ai/agents --skill code-g2i-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code
Source: https://github.com/g2i-ai/agents/tree/main/skills/code
Command: npx skills add https://github.com/g2i-ai/agents --skill code-g2i-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement production changes in a codebase by following an explicit spec, reducing manual drift and aligning with established patterns.

Core Features & Use Cases

  • Spec-driven implementation that follows the provided guidance to deliver feature work or fixes.
  • Minimal, coherent changes that minimize risk and review effort.
  • Conforms to the project's architecture, style, and testing conventions to ensure maintainability.

Quick Start

Provide the task spec path when the work is spec-driven, then implement the smallest coherent change that satisfies the spec.

Frequently Asked Questions about code

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

FAQPage Schema
How do I implement production code changes from a spec while minimizing drift?▼

Spec-driven code implementation automates production changes by following an explicit spec, enforcing the smallest coherent change to reduce manual drift and align with established project patterns.

What is the best way to ensure new feature code conforms to existing project conventions?▼

To ensure code conforms to project conventions, the implementation process validates modifications against existing architecture, style, and testing patterns before applying changes to the repository.

Can I use automated code changes for bug fixes in spec-driven workflows with tests and linting?▼

Yes, automated code changes support common software-engineering tasks like bug fixes and feature work within spec-driven workflows that include tests, linting, and reviews.

How do I start applying a spec to modify a codebase?▼

To start applying a spec, provide the task spec path so the implementation can deliver the smallest coherent change that satisfies the spec and passes project validations.

What are the limitations of automated spec-driven code implementation?▼

Automated spec-driven implementation requires a provided spec path to function and focuses on minimal, coherent changes, meaning it may not suit large-scale architectural rewrites lacking explicit spec guidance.

Does spec-driven code implementation work without predefined project conventions?▼

Spec-driven implementation relies on established project conventions to ensure maintainability, so it works best when existing architecture, style, and testing patterns are already defined.

Related Skills

Explore More Software Engineering Skills→
notquenotque
415

go-sapcc-conventions

Enforce SAP Converged Cloud Go coding conventions in sapcc repositories.

Community
Advanced
RebornQRebornQ
52

trellis-check

Run spec compliance, lint, type-check, and test suites on new changes.

Community
Advanced
ak8458ak8458

Testing Blocks

Validate AEM Edge Delivery code changes with Vitest unit tests and Playwright browser checks.

Community
Intermediate
kslhunterkslhunter
2

sd-tdd

Enforce test-first development with Red-Green-Refactor for regression protection.

Community
Intermediate