update-permissions

Copy .claude/settings.json from the ai-dev framework to a target project.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/aifuun/u-safe-archive --skill update-permissions-aifuun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-permissions
Source: https://github.com/aifuun/u-safe-archive/tree/main/.claude/skills/update-permissions
Command: npx skills add https://github.com/aifuun/u-safe-archive --skill update-permissions-aifuun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the manual and error-prone task of updating permission configuration by copying the framework's .claude/settings.json into a target project, ensuring consistent permission settings across repositories.

Core Features & Use Cases

  • One-file deterministic sync: Performs a complete replacement of the target .claude/settings.json using a simple copy operation.
  • Pre-flight validation: Verifies the source is the ai-dev framework directory and that the target path exists, creating the target .claude directory if necessary.
  • Fast and explicit: Designed for framework upgrades, monthly maintenance, or selective permission fixes where a predictable, atomic replacement is required.

Quick Start

From the ai-dev framework directory run /update-permissions ../my-project to copy the .claude/settings.json into the target project.

Frequently Asked Questions about update-permissions

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

FAQPage Schema
How do I sync permission settings from the ai-dev framework to another project?

To sync permission settings, run the tool from the ai-dev directory and specify the target project path. It copies the .claude/settings.json file directly into the target repository, performing a complete replacement of the existing configuration.

What is the best way to update .claude/settings.json across multiple repositories during a framework upgrade?

Updating .claude/settings.json across repositories is handled by copying the framework's source file to each target path. This deterministic file replacement ensures every project receives identical permission settings without manual editing.

Does the permission sync process validate the target directory before copying files?

Yes, the permission sync process validates the target directory path before copying. It also verifies the existence of the source .claude/settings.json file and automatically creates the target .claude directory structure if it is missing.

When do I need to replace the .claude/settings.json file in a target project?

You need to replace the .claude/settings.json file during framework upgrades, monthly maintenance routines, or when applying selective permission fixes. This ensures the target project aligns with the framework's current permission configurations.

Why does my target project still have outdated permissions after a framework update?

Outdated permissions after a framework update occur when the .claude/settings.json file is not copied to the target project. Running the sync tool from the ai-dev directory performs the complete file replacement needed to update permissions.

Can I use this permission sync tool to update a specific subset of settings in the target file?

No, you cannot update a specific subset of settings because the tool performs a complete file replacement. It copies the entire .claude/settings.json file from the ai-dev framework, overwriting all existing permissions in the target project.