edit-dot-claude

Edits .claude/ configuration files via /tmp working copies to reduce permission prompts.

3|Updated Jun 7, 2026
One-click install
npx skills add https://github.com/MLShukai/ResoniteIO --skill edit-dot-claude-mlshukai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edit-dot-claude
Source: https://github.com/MLShukai/ResoniteIO/tree/main/.claude/skills/edit-dot-claude
Command: npx skills add https://github.com/MLShukai/ResoniteIO --skill edit-dot-claude-mlshukai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Editing files under .claude/ (agents, skills, commands) triggers a permission prompt on every Edit or Write operation, which becomes tedious when creating or revising multiple files. This Skill defines a workflow that stages changes in /tmp (an allowed directory) and copies them back with a single auto-approved cp command. ## Core Features & Use Cases - Staging workflow: Copy target files to /tmp/dot-claude-work/, edit freely without prompts, then copy results back into .claude/. - New file creation: Write new SKILL.md, agent, or command files in /tmp first, then place them under the correct .claude/ subdirectory. - Scope guidance: Covers .claude/agents/*.md, .claude/skills/<name>/SKILL.md, and .claude/commands/*.md, while delegating settings.json changes to the update-config skill. - Use Case: When creating a new skill that needs five rounds of edits to its SKILL.md, you perform all edits in /tmp with zero prompts and finish with one auto-approved copy command instead of approving five prompts. ## Quick Start Copy the .claude file I want to edit into /tmp/dot-claude-work, make the edits there, and copy it back into .claude when done.

Frequently Asked Questions about edit-dot-claude

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

FAQPage Schema
How do I edit .claude files without repeated permission prompts?

Copy the target file or directory to /tmp/dot-claude-work, perform all Edit and Write operations there without prompts, then copy the result back into .claude with a single cp command that is auto-approved by the allowlist.

How to create a new Claude Code skill or agent file?

Create the file under /tmp/dot-claude-work/<name> first, then copy it into the correct location such as .claude/skills/<name>/SKILL.md for skills or .claude/agents/<name>.md for agents.

Should I edit .claude/settings.json with this /tmp workflow?

No, settings.json and settings.local.json should be handled through the update-config skill instead, because it shares logic for permission schema validation and hooks configuration.

Why does rm -rf fail when cleaning up /tmp working directories?

The rm -rf command pattern is denied in the permission configuration. Use rm -r without the force flag to remove stale working directories under /tmp/dot-claude-work before starting a new task.

What are the limitations of copying edited files back with cp?

A plain cp -r does not propagate deletions, so files removed in the /tmp copy remain in the destination. You must delete extra files in the target directory individually after syncing.