promote-permissions

Identify and promote ephemeral permissions to versioned settings with commits and PRs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nicolasrouanne/claude --skill promote-permissions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: promote-permissions
Source: https://github.com/nicolasrouanne/claude/tree/main/.claude/skills/promote-permissions
Command: npx skills add https://github.com/nicolasrouanne/claude --skill promote-permissions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ephemeral permissions scattered across local and project configurations cause drift and inconsistencies. This Skill promotes approved permissions to versioned settings to ensure stable, auditable policy across environments.

Core Features & Use Cases

  • Scan ephemeral permissions in user-level and project-level settings
  • Compare against versioned settings and propose promotions
  • Create commits and PRs to propagate changes to the appropriate repos

Quick Start

Promote ephemeral permissions from local to versioned settings and create PRs for updated repos.

Frequently Asked Questions about promote-permissions

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

FAQPage Schema
How do I promote ephemeral permissions to versioned settings?

To promote ephemeral permissions to versioned settings, the Skill scans local and project configurations, identifies unversioned permissions, and generates commits and PRs to propagate the changes to the appropriate git repositories.

What is ephemeral permissions drift in project settings?

Ephemeral permissions drift occurs when local and project configurations contain unversioned permissions, causing inconsistencies across environments. The Skill resolves this by promoting approved permissions to versioned settings for stable, auditable policy.

How do I automate creating PRs for updated settings files?

You can automate creating PRs for updated settings files by applying the promotion workflow, which generates commits and PRs for each repository as appropriate after comparing local ephemeral permissions against versioned files.

Does the permissions promotion workflow require a git repository?

Yes, the permissions promotion workflow requires a git repository, as it enforces checks for git repository presence, correct file paths, and ensures changes align with destination rules before generating commits.

What's the best way to audit ephemeral permissions across multiple projects?

The best way to audit ephemeral permissions across multiple projects is to scan user-level and project-level settings, compare them against versioned settings, and propose promotions to ensure policy is stable and auditable.

What happens if file paths are incorrect during permissions promotion?

If file paths are incorrect during permissions promotion, the workflow enforces checks for correct file paths and stops, ensuring changes only proceed when they align with the described destination rules for versioned settings.