add-feature

Plan and implement major OhMyCode feature additions with test-first development.

131|4|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/AlphaLab-USTC/OhMyCode --skill add-feature-alphalab-ustc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-feature
Source: https://github.com/AlphaLab-USTC/OhMyCode/tree/main/.agents/skills/add-feature
Command: npx skills add https://github.com/AlphaLab-USTC/OhMyCode --skill add-feature-alphalab-ustc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides you through adding a new major feature to OhMyCode when the request goes beyond existing extension points like tools or providers, helping you change the core codebase in a controlled way.

Core Features & Use Cases

  • Architecture Planning: Determines where new code should live, what interfaces it should expose, and which existing modules must change.
  • Test-Driven Implementation: Follows a strict TDD workflow with failing tests first, minimal code changes, and full regression checks.
  • Repository-Specific Guidance: Requires reading the development guide before coding so changes match OhMyCode’s conventions, dependency graph, and commit style.
  • Use Case: A developer asks for hook support, MCP integration, or a new CLI command, and this Skill maps the feature into the project structure and implementation steps.

Quick Start

Ask me to add a new feature to OhMyCode and I will first review the development guide, propose the architecture, and then implement it with tests.

Frequently Asked Questions about add-feature

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

FAQPage Schema
How do I add major new features like hooks or MCP support to OhMyCode?

To add major OhMyCode features like hooks or MCP support, this Skill maps the request into the project structure, proposes architecture-aware designs, and implements changes with a test-driven workflow.

What is the best way to implement new CLI commands without breaking the existing module graph?

The best way to implement new CLI commands safely is through minimal surgical code changes guided by architecture planning, ensuring the module graph and existing conventions remain intact.

Do I need to read the development guide before adding multi-session management capabilities?

Yes, you need to read the development guide before coding multi-session management to ensure your changes match OhMyCode's dependency graph, conventions, and commit style.

Can I use test-driven development to safely build a plugin system for OhMyCode?

Yes, you can use test-driven development to build a plugin system by writing failing tests first, making minimal code changes, and running full regression checks throughout the implementation.

When do I need architecture-aware design for feature development beyond existing extension points?

You need architecture-aware design for feature development when requests go beyond existing tools or providers, requiring changes to the core codebase to expose new interfaces or modify existing modules.

Why does adding core capabilities require updating documentation when the module graph changes?

Updating documentation when the module graph changes is required because adding core capabilities alters existing module relationships, and documentation keeps the architecture-aware design consistent for future development.