Skip to content
Back to skills

Update Claude Md

ASecurity

After any correction from the user, update CLAUDE.md with a rule to prevent the same mistake from recurring. Use when the user corrects your behavior or says "don't do that again". Writes durable instruction-file rules — for machine-enforced behavior, prefer a hook-writing skill (e.g. hookify) or settings changes when available.

  • 10 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
ai-agentsgobashgit

Works with

  • cursor

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 11, 2026

npx -y skills add rajitsaha/100xprism --skill update-claude-md --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Update Claude Md?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Update Claude Md
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rajitsaha-update-claude-md/badge)](https://www.skillsdirectory.com/skills/rajitsaha-update-claude-md)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: update-claude-md
description: After any correction from the user, update CLAUDE.md with a rule to prevent the same mistake from recurring. Use when the user corrects your behavior or says "don't do that again". Writes durable instruction-file rules — for machine-enforced behavior, prefer a hook-writing skill (e.g. hookify) or settings changes when available.
category: engineering
tier: on-demand
slash_command: /update-claude
allowed-tools: Read Edit Write
model: haiku
---

# Update-Claude — CLAUDE.md Rule Writer

After any correction, update CLAUDE.md with a rule to prevent the same mistake recurring.

## How to use
- `/update-claude` — after a correction, write a rule to CLAUDE.md

---

## Phase 1 — Identify the pattern

What went wrong? What should have been done instead? Be specific — one clear pattern, not a vague note.

---

## Phase 2 — Write a rule

Formulate as a clear, actionable rule:
```
- [Rule]: [What to do / not to do]. Why: [brief context].
```

Short rules stick. Long paragraphs get ignored.

---

## Phase 3 — Update CLAUDE.md

```bash
PROJECT_ROOT=$(git rev-parse --show-toplevel)
INSTRUCTION_FILE=$(for f in CLAUDE.md AGENTS.md .cursorrules; do [ -f "$PROJECT_ROOT/$f" ] && echo "$PROJECT_ROOT/$f" && break; done)
```

Append the rule under a `## Rules` or `## Corrections` section in the project's instruction file. If no instruction file exists, create `CLAUDE.md` in the project root.

---

## Phase 4 — Confirm

Tell the user: "Updated [file] with: [rule summary]"

If the rule isn't reducing mistakes after 2–3 sessions: rewrite it — be more specific or more prominent.

Files in this skill

  • .100xprism-generated89 B
  • SKILL.md1.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.