code

Implement features, fix bugs, and refactor code with tests.

1|1|Updated Feb 28, 2024
One-click install
npx skills add https://github.com/jiyeol-lee/dotfiles --skill code-jiyeol-lee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code
Source: https://github.com/jiyeol-lee/dotfiles/tree/main/.opencode/skills/code
Command: npx skills add https://github.com/jiyeol-lee/dotfiles --skill code-jiyeol-lee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, repeatable approach for implementing features, fixing bugs, refactoring code, and validating changes with unit and integration tests in modern software projects.

Core Features & Use Cases

  • Understand requirements by reviewing existing code to preserve conventions
  • Plan changes, edge cases, and dependencies before touching the code
  • Implement changes following project patterns and run verification checks
  • Verify changes with a completion checklist and communicate results
  • Report blockers and ambiguities to orchestrator — do NOT guess

Quick Start

Begin by reading the requirement, plan the changes, implement code, and verify with tests.

Frequently Asked Questions about code

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

FAQPage Schema
How do I implement features and fix bugs while preventing regressions?

To implement features and fix bugs while preventing regressions, follow a structured workflow: review existing code, plan changes and edge cases, implement modifications, and validate with unit and integration tests.

What is the best way to refactor code and ensure existing conventions are preserved?

The best way to refactor code while preserving conventions is to review the existing project structure first, plan dependencies and edge cases, implement changes following established patterns, and verify results with a completion checklist.

How does automated unit and integration testing work during code enhancement?

Automated unit and integration testing during code enhancement works by validating implemented changes against planned edge cases, running verification checks, and ensuring no regressions occur before reporting completion.

Can I use this workflow for collaborative team projects with complex dependencies?

Yes, you can use this workflow for collaborative team projects as it supports scenarios from feature addition to bug fixes, handles complex dependencies, and reports blockers or ambiguities to the orchestrator instead of guessing.

What should I do when requirements are ambiguous during code implementation?

When requirements are ambiguous during code implementation, you should report the blockers and ambiguities to the orchestrator rather than guessing, ensuring changes align with project conventions and preventing regressions.

How do I generate and run tests for a new feature implementation?

To generate and run tests for a new feature implementation, plan the edge cases first, implement the code changes per project conventions, then generate unit and integration tests to validate the modifications and prevent regressions.