learn-from-manual-edits

Detects user manual edits on agent-written code and persists inferred preferences as project conventions.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/byron1st/personal-harness --skill learn-from-manual-edits-byron1st
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: learn-from-manual-edits
Source: https://github.com/byron1st/personal-harness/tree/main/skills/learn-from-manual-edits
Command: npx skills add https://github.com/byron1st/personal-harness --skill learn-from-manual-edits-byron1st

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you manually fix code an AI agent wrote, that feedback is usually lost — the agent repeats the same mistake next session. This Skill captures those manual edits, infers the general coding preference behind each one, and records them as durable conventions in the project's AGENTS.md or CLAUDE.md so corrections never need to be made twice. ## Core Features & Use Cases - Edit Attribution: Separates your manual edits from the agent's own uncommitted changes in the working tree by reconstructing what the agent wrote and diffing against current content, asking you when attribution is ambiguous. - Preference Generalization: Filters edits to keep only those that generalize — style, structure, naming, error handling, testing patterns — while excluding one-off bug fixes and business-logic corrections. - Persistent Convention Log: Maintains a dated, deduplicated "Conventions Learned from Manual Edits" section in CLAUDE.md or AGENTS.md, refining or replacing rules as preferences evolve. - Use Case: After a long coding session, you tell the agent you tweaked its output. The skill identifies your hunks, records rules like "wrap errors with fmt.Errorf including the failed operation", and applies them to all subsequent code. ## Quick Start Tell the agent: I manually changed some of the code you wrote — learn from my edits and record the conventions.

Frequently Asked Questions about learn-from-manual-edits

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

FAQPage Schema
How do I make an AI coding agent learn from my manual edits?▼

Tell the agent you manually changed code it wrote. The skill diffs the working tree against what the agent wrote, infers the general preference behind each of your edits, and records them as convention rules in CLAUDE.md or AGENTS.md for future sessions.

How does the skill separate my edits from the agent's changes in git?▼

Git alone cannot separate uncommitted agent and user edits, so the skill reconstructs the version the agent wrote from session context and diffs it against current file content. Files the agent never touched are attributed entirely to you.

What kinds of edits get recorded as coding conventions?▼

Only edits that generalize: style, naming, error handling, architecture, and testing patterns that apply beyond one file and are forward-actionable. One-off bug fixes, business-logic corrections, and typos are reported but not persisted.

Where are the learned conventions stored?▼

Conventions are stored in a dedicated section of the project root instruction file — CLAUDE.md if it exists, otherwise AGENTS.md, creating CLAUDE.md if neither exists. Rules are grouped under headings like Style, Architecture, and Errors with dates.

What happens when attribution of an edit is uncertain?▼

When the agent cannot faithfully reconstruct what it wrote — for example after a long or compacted session — it shows you the ambiguous hunks and asks which are yours rather than guessing, since a wrong attribution recorded as a convention is worse than a question.