code-change-approval

Require explicit user approval before modifying files or installing packages.

1|Updated Dec 17, 2016
One-click install
npx skills add https://github.com/vm-wylbur/pb-dotfiles --skill code-change-approval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-change-approval
Source: https://github.com/vm-wylbur/pb-dotfiles/tree/main/ai/claude-code/skills/code-change-approval
Command: npx skills add https://github.com/vm-wylbur/pb-dotfiles --skill code-change-approval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unintended or unapproved code changes can introduce bugs, security vulnerabilities, or deviate from project standards. This skill prevents such issues by enforcing a strict approval process, ensuring every modification is intentional and verified.

Core Features & Use Cases

  • Pre-Change Research: Automatically checks for existing functionality, preventing duplication or unnecessary modifications, and ensuring changes are made in the right place.
  • Explicit Approval Workflow: Requires user confirmation for all file modifications, destructive operations (like deleting files), and package installations, giving you full control over changes.
  • Clear Communication: Presents proposed changes, their reasons, and potential impacts in a structured, easy-to-understand format, allowing for informed decisions.
  • Use Case: When asked to "add JWT authentication to the API", the skill will first research existing authentication logic, then propose specific file changes (e.g., src/auth.ts), detailing what will change and why, and wait for explicit user approval before executing.

Quick Start

Change the database connection string in config.py. The skill will ask for approval, detailing the proposed change before executing.

Frequently Asked Questions about code-change-approval

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

FAQPage Schema
How do I prevent unintended code changes in my projects?

Code-change approval enforces explicit user confirmation before modifying files, installing packages, or performing destructive operations. This approval-driven workflow requires you to review and authorize each change, preventing accidental modifications that could introduce bugs or security vulnerabilities.

What happens before a file modification is executed?

Before any file edit, the approval process surfaces a structured change-request template detailing what will change, why, and potential impacts. It also performs pre-change research to check existing functionality, ensuring modifications happen in the right place and don't duplicate existing logic.

Can I use code approval to manage package installations?

Yes. Code-change approval requires explicit user confirmation for package installations alongside file modifications and destructive operations. This gives you full control over dependency changes and prevents unauthorized packages from being added to your project.

When should I use code approval for system configuration changes?

Use code approval whenever you modify system configurations to ensure intentional, verified changes. The skill blocks execution until you confirm, making it essential for configuration files where unintended edits can break environments or compromise security.

Does code approval recommend dry-runs for risky operations?

Yes. For destructive operations, code approval recommends running dry-runs before execution. This lets you preview the impact of deletions or major rewrites, reducing the risk of unrecoverable changes to your codebase.

How does code approval fit into a development workflow?

Code approval integrates into git-based workflows by intercepting file edits, deletions, and package installs. It surfaces change requests with reasoning and impact analysis, making it a safety layer for collaborative development, refactoring, and security-sensitive modifications.