developer-implementation

Implement approved ytnova tasks in C with minimal coherent edits.

12|1|Updated Oct 31, 2025

Search Tags:#c #software-engineering #invariants #proof #build-and-test #minimal-change #architectural-safety

Ready to run

npx skills add https://github.com/robkam/ytreenova --skill developer-implementation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: developer-implementation
Source: https://github.com/robkam/ytreenova/tree/main/.ai/skills/developer-implementation
Command: npx skills add https://github.com/robkam/ytreenova --skill developer-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides developers to implement approved ytnova tasks in C with minimal, coherent edits while preserving architectural safety and providing terminal-verified proof of changes.

Core Features & Use Cases

Smallest coherent change set: identify affected symbols and apply minimal modifications.
Architectural safety and invariants: preserve context passing, isolation, and rationale in code comments.
Build, test, and evidence: require compilation, test execution, and explicit evidence of results.

Quick Start

Apply this skill to implement a new C feature by locating affected symbols, making the minimal coherent edit, and validating with builds and tests.

Frequently Asked Questions about developer-implementation

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

FAQPage Schema

How do I implement C features while preserving architectural safety?▼

To implement C features with architectural safety, identify affected symbols and apply minimal coherent edits that preserve context passing and isolation. This approach enforces invariants and documents rationale in code comments to maintain structural integrity throughout the modification process.

What is a minimal coherent change set in C software engineering?▼

A minimal coherent change set in C software engineering is the smallest possible set of modifications applied to affected symbols. It ensures that changes remain isolated and coherent, preserving architectural invariants while avoiding unnecessary alterations to the existing codebase.

How do I verify C code changes with terminal evidence after a build?▼

To verify C code changes, you must compile the code, execute tests, and capture explicit terminal evidence of the results. This terminal-verified proof confirms that the modifications compile successfully and pass test execution without breaking existing functionality.

Do I need to document rationale when making minimal code edits in C?▼

Yes, documenting rationale is required when making minimal code edits in C. You must preserve rationale in code comments to maintain architectural safety, ensuring that future developers understand the context passing, isolation decisions, and invariant enforcement behind the modifications.

What's the best way to report completion evidence for C task implementations?▼

The best way to report completion evidence for C task implementations is to compile a summary of changed files and test results. This report must include terminal-verified proof of compilation, test execution outcomes, and explicit evidence demonstrating that the minimal coherent edits satisfy the task scope.

When should I not use minimal change sets for C implementations?▼

You should not use minimal change sets for C implementations when the task scope requires broad architectural refactoring rather than targeted modifications. If the changes cannot preserve existing invariants, context passing, or isolation, a minimal coherent edit approach will not maintain architectural safety.