agentleFS
ohanyanohanyan/adulting/skills/repair/SKILL.md

repair

Skill1 starsChanged 7 months agoMITView on GitHub

Post-conflict repair. Within 24 hours of a rupture (snap, yell, dismissive moment, missed bid), a structured 7-step repair. Usage is /repair [person]. Works with spouse, kid, parent, colleague.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 11 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every relationship will have ruptures: a snap, a yell, a dismissal, a phone-scroll while they were trying to connect, a joke at their …

    line 10
  2. Distinctive:

    If missing, ask: "Who is the repair for?"

    line 18
  3. Distinctive:

    Ask the user to describe it briefly.

    line 22
  4. Distinctive:

    If they start explaining "why they did it" (I was tired, I was stressed, they were being...), gently redirect: "That's context for you.

    line 28
  5. Distinctive:

    If the person is not ready for physical contact, respect that.

    line 76
  6. Distinctive:

    After any rupture with a child, three sentences:

    line 80
  7. Distinctive:

    Ask the user: "Is this the first time, or is this a pattern?"

    line 90
  8. Distinctive:

    If a pattern — same rupture with the same person for the third time or more — the issue is not the rupture.

    line 92
  9. Very specific:

    Run /hard-conversation about the pattern itself, once the immediate repair has landed.

    line 93
  10. Distinctive:

    Consider therapy, couple's therapy, or coaching if this is about ongoing dynamics.

    line 94
  11. Distinctive:

    Do not delay. Ideally same day.

    line 98
  12. Distinctive:

    If you cannot do it today (for logistical reasons), at least send a brief message: "I owe you a real apology for [x].

    line 105

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/repair

What separates secure relationships from anxious ones is not the absence of rupture. It is the presence of repair.

Every relationship will have ruptures: a snap, a yell, a dismissal, a phone-scroll while they were trying to connect, a joke at their expense. What matters is whether it gets repaired, specifically, within 24 hours.

This skill walks you through it.

Usage

$ARGUMENTS should be the person. "Partner." "Son Lucas." "Mom." "Subbu."

If missing, ask: "Who is the repair for?"

Step 1: What actually happened

Ask the user to describe it briefly. Neutrally if possible. No "but they did X first."

Capture:

  • What I did or said (behavior).
  • What I think the impact was on them.

If they start explaining "why they did it" (I was tired, I was stressed, they were being...), gently redirect: "That's context for you. The repair is about them. What was the impact on them?"

Step 2: The 7-step repair

This is the protocol. It works with any close person, modified slightly for kids.

1. Take responsibility plainly, with no "but."

Wrong: "I'm sorry I yelled, but you were being..." Right: "I'm sorry I yelled. That was me, not you."

Help the user draft the one sentence. It should be a clean sentence that owns the specific behavior. "I snapped at you tonight." "I talked over you in that meeting." "I got on my phone while you were telling me about your day. That was wrong of me."

2. Name the impact, not the intent.

"I can see that hurt you. That makes sense. You deserved better than that."

NOT: "I didn't mean to..." (This is about you.) NOT: "I'm sorry you feel that way..." (This is not a repair, it is a deflection.)

3. Let the apology land. Do not rush.

Most people, after apologizing, immediately move to explain or justify. Resist.

Silence is okay. They may need 5 seconds, 30 seconds, or 5 minutes. Do not fill it.

4. Ask what they needed.

"What did you need from me in that moment that you didn't get?"

This question is a gift. Most people have never been asked it. They will often pause and, if they answer honestly, give you the map for the rest of the relationship.

Listen to the answer. Write it down after. Do not respond with "well but I also needed...".

5. Offer the structural repair.

"Next time I feel that rising in me, here is what I will try to do instead."

Specific. Observable. A behavior, not a feeling. "Next time I feel that surge of frustration, I am going to say 'I need ten minutes' and leave the room, not snap at you."

6. Reconnect physically (if welcomed).

For spouse: a hand, a hug, eye contact. Not sex. Not yet. Reconnection first.

For kid: a hug, a snuggle, a hand on the back. Sitting with them silently for a minute.

For friend or colleague: a handshake, a hand on the shoulder, or just warm eye contact. Match the relationship's norms.

If the person is not ready for physical contact, respect that. Do not insist. The repair does not require their affection.

7. (For kids only) The Three Lines.

After any rupture with a child, three sentences:

  1. "I love you no matter what."
  2. "You are a good kid."
  3. "You didn't deserve that."

These three sentences, delivered sincerely, protect a child from internalizing the rupture as a story about themselves.

Step 3: The structural question

Ask the user: "Is this the first time, or is this a pattern?"

If a pattern — same rupture with the same person for the third time or more — the issue is not the rupture. It is the underlying structural thing. Suggest:

  • Run /hard-conversation about the pattern itself, once the immediate repair has landed.
  • Consider therapy, couple's therapy, or coaching if this is about ongoing dynamics.

Step 4: Deliver the repair

Do not delay. Ideally same day. Absolutely within 24 hours.

  • In person is best.
  • Voice call is second.
  • Video call is third.
  • Text is a last resort and only appropriate for minor ruptures with peers.

If you cannot do it today (for logistical reasons), at least send a brief message: "I owe you a real apology for [x]. I want to do it right, not over text. Can we talk tonight?" This holds the space.

Step 5: Log

Append to ~/adulting-data/journal/repair-log.md:

# <date>

Person: <...>
Rupture: <what I did>
Delivered repair: <where and when>
What they said they needed: <...>
Structural change I committed to: <...>
Pattern check: <first time | recurring | pattern>

The underlying belief

The goal is not to never rupture. The goal is to become excellent at repair.

A parent who never yells is either lying to themselves or so emotionally shut down their kids can't reach them. The parent to be is the one who yells less over time, and repairs every time.

A partner who never disappoints is fiction. The partner to be is the one who owns their disappointment cleanly when it happens.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.