edit-skill

Edit and publish skill changes in a Git repository with pull requests.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/butterflyskies/claude-skills --skill edit-skill-butterflyskies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edit-skill
Source: https://github.com/butterflyskies/claude-skills/tree/main/edit-skill
Command: npx skills add https://github.com/butterflyskies/claude-skills --skill edit-skill-butterflyskies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of modifying existing skills or creating new ones within a Git repository, automating the entire workflow from editing to pull request creation.

Core Features & Use Cases

  • Skill Modification: Edit existing skill files based on descriptive arguments.
  • New Skill Creation: Generate new skill directories and SKILL.md files.
  • Automated Git Workflow: Handles branching, committing, pushing, and Pull Request creation.
  • Use Case: You need to add a new feature to an existing skill, like improving its error handling. You describe the change, and the skill automatically updates the relevant files, commits them, and opens a PR.

Quick Start

Use the edit-skill to add a Phase 6 for documentation generation to the develop skill.

Frequently Asked Questions about edit-skill

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

FAQPage Schema
How do I automate git pull request creation for code changes?

Automating git pull request creation for code changes is handled by branching, committing, pushing, and opening a PR automatically after you describe the desired modifications to your skill files.

What is the best way to create and publish new skills in a git repository?

Creating and publishing new skills in a git repository involves generating a new skill directory and SKILL.md file, then automating the git workflow to commit and push those changes directly to a configured GitHub origin.

Do I need a pre-initialized git repository with branch protection to edit skills?

Yes, editing skills requires a pre-initialized git repository located at ~/.claude/skills with a GitHub origin configured and branch protection enabled on the main branch to manage workflow changes.

Can I modify existing skill files without manually handling git branching?

Yes, you can modify existing skill files by providing descriptive arguments for the changes, and the automation handles the entire git branching, committing, and pushing workflow without manual intervention.

What are the limitations of automating skill modifications through git workflows?

Limitations include relying entirely on a pre-initialized repository at ~/.claude/skills with a configured GitHub origin and branch protection on main, meaning it cannot operate without this specific environment setup.