Openclaw Repair Sweep
openclaw/openclaw
Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.
Repair a relationship after an argument — reconnect, own your part, and rebuild trust — instead of the cold silence that lets damage set.
MITAuto-check passed
Install Repair After A Fight
$ npx skills add mohitagw15856/pm-claude-skills --skill repair-after-a-fight -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills repair-after-a-fight --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/repair-after-a-fight .claude/skills/repair-after-a-fight && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "repair-after-a-fight" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/repair-after-a-fight into .claude/skills/repair-after-a-fight/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repair-after-a-fight", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/repair-after-a-fightType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill repair-after-a-fight -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills repair-after-a-fight --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/repair-after-a-fight .agents/skills/repair-after-a-fight && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "repair-after-a-fight" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/repair-after-a-fight into .agents/skills/repair-after-a-fight/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repair-after-a-fight", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill repair-after-a-fight -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills repair-after-a-fight --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/repair-after-a-fight .cursor/skills/repair-after-a-fight && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "repair-after-a-fight" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/repair-after-a-fight into .cursor/skills/repair-after-a-fight/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repair-after-a-fight", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/repair-after-a-fight--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill repair-after-a-fight -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills repair-after-a-fight --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/repair-after-a-fight .gemini/skills/repair-after-a-fight && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "repair-after-a-fight" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/repair-after-a-fight into .gemini/skills/repair-after-a-fight/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repair-after-a-fight", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills repair-after-a-fightInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill repair-after-a-fight -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/repair-after-a-fight .github/skills/repair-after-a-fight && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "repair-after-a-fight" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/repair-after-a-fight into .github/skills/repair-after-a-fight/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repair-after-a-fight", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill repair-after-a-fight -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills repair-after-a-fight --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/repair-after-a-fight .opencode/skills/repair-after-a-fight && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "repair-after-a-fight" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/repair-after-a-fight into .opencode/skills/repair-after-a-fight/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repair-after-a-fight", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
repair-after-a-fight- GitHub stars
- 1.4k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 601 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Repair a relationship after an argument — reconnect, own your part, and rebuild trust — instead of the cold silence that lets damage set.
- Works in 6 steps: Find the real hurt. The topic of the… → Own your part specifically. A genuine "I… → Acknowledge their hurt. Show you… → …
- Asked how do I make up after a fight
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Reconnect, Own,… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Repair After A Fight is an agent skill from mohitagw15856/pm-claude-skills. 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…
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked how do I make up after a fight
- Repair things after an argument
- Reconnect after we fought
- Fix things with someone I hurt
Example prompts
- “/repair-after-a-fight”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Find the real hurt. The topic of the fight is often not the wound — underneath is usually feeling unheard, disrespected, or unsupported…
- Own your part specifically. A genuine "I was wrong to X, and I can see it hurt you" repairs; a defensive "I'm sorry but you..." or "sorry…
- Acknowledge their hurt. Show you understand how it landed for them, without rushing to defend or explain — feeling understood is most of…
- Reopen without reigniting. Break the silence with warmth and ownership, not a re-litigation of who was right.
- Rebuild, don't just bury. Move past "let's forget it" toward actually understanding what happened and how to handle it better — that's…
- Do your part regardless. You can own your side without them owning theirs; leading the repair often unlocks theirs, but don't make yours…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Repair After A Fight loads about 1.2k tokens when it runs. Until then it costs about 158 tokens; SKILL.md has 601 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 601 words, ~1,175 tokens.
Download SKILL.mdSave it as
.claude/skills/repair-after-a-fight/SKILL.md (or your agent's skills folder).- name
- repair-after-a-fight
- description
- 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 never fighting.
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 — what it was about and what was said/done
- Your part — honestly, what you contributed (defensiveness here blocks repair)
- The relationship — partner, friend, family, and how it usually goes
- Where it stands — cold silence, a tense truce, or still raw
- Your goal — genuinely repair, or just end the standoff
Framework: Reconnect, Own, Rebuild
- Find the real hurt. The topic of the fight is often not the wound — underneath is usually feeling unheard, disrespected, or unsupported. Repair the real thing.
- Own your part specifically. A genuine "I was wrong to X, and I can see it hurt you" repairs; a defensive "I'm sorry but you..." or "sorry you feel that way" makes it worse. Take your actual part.
- Acknowledge their hurt. Show you understand how it landed for them, without rushing to defend or explain — feeling understood is most of repair.
- Reopen without reigniting. Break the silence with warmth and ownership, not a re-litigation of who was right.
- Rebuild, don't just bury. Move past "let's forget it" toward actually understanding what happened and how to handle it better — that's what restores trust.
- Do your part regardless. You can own your side without them owning theirs; leading the repair often unlocks theirs, but don't make yours conditional.
Show full SKILL.md (215 more words)Show less
Output Format
Repair with: [person] · the fight: [what happened] · now: [silence/tense/raw]
What actually needs repairing: [surface incident vs the deeper hurt]. Own your part: [the specific thing you did — genuinely, not defensively]. Acknowledge their hurt: "[show you get how it landed]". Reopen with:
[Warm, owning, not re-litigating — breaks the silence]. Rebuild: [understand what happened + how to handle it better] — not just "let's forget it". Your part, regardless: do it without making it conditional on theirs.
Quality Checks
- Distinguishes the surface incident from the deeper hurt
- Owns a specific part genuinely (no defensive non-apology)
- Acknowledges the other person's feelings
- Reopens warmly without re-litigating the fight
- Aims to rebuild trust, not just bury it
- Encourages doing one's own part unconditionally
Anti-Patterns
- A defensive "sorry but you..." non-apology.
- "Sorry you feel that way" — the opposite of repair.
- Rushing to move on without understanding what happened.
- Making your apology conditional on theirs.
- Re-litigating who was right in the reopening.
Example Trigger Phrases
- "I had a bad fight with my partner — how do I make up?"
- "How do I repair things after an argument with my friend?"
- "We fought and now it's just cold silence. Help me reconnect."
- "I hurt someone in an argument and want to fix it."
- "What do I say to make up after a big blowup?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/repair-after-a-fight of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Repair After A Fight next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Repair After A Fight this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Openclaw Repair Sweepopenclaw/openclaw | 392k | — | ~1.8k | Automated safety check: Pass | MIT | |
| TDD Repairruvnet/ruflo | 74k | — | ~1.6k | Automated safety check: Notes | MIT | |
| Step Partsearthtojake/text-to-cad | 19k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| ReconnectSeemSeam/claude_codex_bridge | 3.6k | — | ~199 | Automated safety check: Pass | Custom licence | |
| ReconnectSeemSeam/claude_codex_bridge | 3.6k | — | ~195 | Automated safety check: Pass | Custom licence |
Similar skills
TDD Repair
ruvnet/ruflo
Test-Driven Repair — given a failing test, spawn a bounded headless claude -p (Read/Edit/Bash only) that makes the test pass without modifying it.
Step Parts
earthtojake/text-to-cad
Find, evaluate, and download common purchasable CAD parts from step.parts, including named off-the-shelf actuators, servos, motors, electronics boards, connectors, screws, bolts, nuts, washers…
Reconnect
SeemSeam/claude_codex_bridge
Enable or disable tmux-bound disconnect recovery for the current Codex thread.
Reconnect
SeemSeam/claude_codex_bridge
Enable or disable tmux-bound disconnect recovery for the current Codex thread.
Carrier Relationship Management
sickn33/agentic-awesome-skills
Codified expertise for managing carrier portfolios, negotiating freight rates, tracking carrier performance, allocating freight, and maintaining strategic carrier relationships.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Repair After A Fight
What does Repair After A Fight do?
Repair a relationship after an argument — reconnect, own your part, and rebuild trust — instead of the cold silence that lets damage set. Repair After A Fight is an agent skill from mohitagw15856/pm-claude-skills. Repair a relationship after an argument — reconnect, own your part, and rebuild trust — instead of the cold silence that lets damage set.
When should I use Repair After A Fight?
Repair After A Fight fits situations like: asked how do I make up after a fight; repair things after an argument; reconnect after we fought; fix things with someone I hurt.
How do I install Repair After A Fight in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill repair-after-a-fight -a claude-code`. Or copy the skill folder (skills/repair-after-a-fight in mohitagw15856/pm-claude-skills) into .claude/skills/repair-after-a-fight in your project. Claude Code loads it when a task matches its description.
How do I install Repair After A Fight in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill repair-after-a-fight -a codex`. Or copy the skill folder (skills/repair-after-a-fight in mohitagw15856/pm-claude-skills) into .agents/skills/repair-after-a-fight in your project. Codex loads it when a task matches its description.
Can I use Repair After A Fight in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill repair-after-a-fight -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/repair-after-a-fight, .gemini/skills/repair-after-a-fight, .github/skills/repair-after-a-fight and .opencode/skills/repair-after-a-fight in your project.
What does Repair After A Fight need to run?
SKILL.md names no scripts, command-line tools or credentials: Repair After A Fight is instructions for the agent only.
Does Repair After A Fight access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Repair After A Fight safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Repair After A Fight use?
Repair After A Fight is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Repair After A Fight use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Repair After A Fight?
Skills that share tags, products or a category with Repair After A Fight: Openclaw Repair Sweep (openclaw/openclaw, 392k stars), TDD Repair (ruvnet/ruflo, 74k stars), Step Parts (earthtojake/text-to-cad, 19k stars) and Reconnect (SeemSeam/claude_codex_bridge, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Repair After A Fight?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.