Agent skill

repair-after-a-fight

Repair a relationship after an argument — reconnect, own your part, and rebuild trust — instead of the cold silence that lets damage set. Use when asked how do I make up after a fight, repair things after an argument, reconnect after we fought, or fix things with someone I hurt. Produces a read on what actually needs repairing (the incident vs the deeper hurt), a genuine repair approach (own your part specifically, acknowledge their hurt, no fake apology), the words to reopen, and how to rebuild rather than just move on — because unrepaired fights compound, and the repair matters more than nev

mohitagw158561,255★ · 1 repos on radarProfile →
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill repair-after-a-fight --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/repair-after-a-fight/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,277
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Repair After a Fight Every relationship has fights — what separates the strong ones isn't never fighting, it's *repairing* well afterward. Left unrepaired, the silence hardens and the resentment compounds. This helps you reconnect: figure out what actually needs mending, own your part specifically (not a defensive non-apology), acknowledge their hurt, and rebuild trust — because the repair is where the relationship is actually made or broken. ## What This Skill Produces - **What needs repairing** — separating the surface incident from the deeper hurt underneath (often "you didn't have my back" matters more than the topic) - **A genuine repair approach** — owning your specific part, acknowledging their feelings, and a real (not defensive or "sorry you feel") apology where warranted - **The reopening words** — how to break the silence and start the repair without reigniting the fight - **The rebuild** — moving from "okay we're past it" to actually restoring trust and understanding what happened - **A both-sides note** — repair usually needs each person to own their part; how to do yours without demanding theirs ## Required Inputs Ask for these if not provided: - **The fight** — wha

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: Reconnect, Own, Rebuild
  4. Output Format
  5. Repair with: [person] · the fight: [what happened] · now: [silence/tense/raw]
  6. Quality Checks
  7. Anti-Patterns
  8. Example Trigger Phrases
More from pm-claude-skills
All skills →
About this skill
What does the repair-after-a-fight skill do?

Repair a relationship after an argument — reconnect, own your part, and rebuild trust — instead of the cold silence that lets damage set. Use when asked how do I make up after a fight, repair things after an argument, reconnect after we fought, or fix things with someone I hurt. Produces a read on what actually needs repairing (the incident vs the deeper hurt), a genuine repair approach (own your part specifically, acknowledge their hurt, no fake apology), the words to reopen, and how to rebuild rather than just move on — because unrepaired fights compound, and the repair matters more than nev

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill repair-after-a-fight --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,277 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going