change_management

Route tracked file modifications through pull requests for owner review.

2|4|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/khoks/ClaudeTrading --skill change-management-khoks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change_management
Source: https://github.com/khoks/ClaudeTrading/tree/main/.claude/skills/change_management
Command: npx skills add https://github.com/khoks/ClaudeTrading --skill change-management-khoks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This skill eliminates the risk of unreviewed, accidental direct commits to the main branch by automating git branch and pull request workflows for all tracked repo changes, ensuring every design, code, or documentation edit goes through proper owner review before merging.

Core Features & Use Cases

  • Dual operation modes: PR mode automatically creates or updates a change branch, stages relevant modified files, commits changes with a clear message, and opens or updates a pull request for owner review; Sync mode checks the status of your open pull request and switches your local repo back to main once the owner merges it.
  • Integrated change detection: Works with the repo's pre-configured hook that reminds you to use this skill whenever you edit tracked files, so you never forget to route changes through the required review process.
  • Use case: If you just tweaked a trading strategy's logic or updated project documentation and want to send it for approval, this skill handles all the git plumbing, commit messaging, and PR creation for you in seconds.

Quick Start

Use the change_management skill to open a pull request for your recent tracked repo changes.

Frequently Asked Questions about change_management

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

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

Automate pull request creation by using a workflow that stages modified files, commits them with a clear message, and opens a pull request via the GitHub CLI. This ensures all repository changes route through owner review instead of direct main branch commits.

What is the best way to prevent accidental direct commits to the main branch?

Preventing accidental direct commits to the main branch requires enforcing a change control workflow that detects tracked file modifications and automatically routes them through a pull request. This guarantees every code or documentation edit undergoes proper review before merging.

How do I sync my local branch after a pull request is merged?

Sync your local branch by checking the status of your open pull request; once the owner merges it, the sync mode switches your local repository back to the main branch, keeping your environment aligned with the latest reviewed changes.

Does this GitHub CLI workflow require branch protection rules?

Using this GitHub CLI workflow requires git for version control operations and the GitHub CLI for pull request and branch protection management, ensuring all tracked modifications are properly routed for owner approval before integration.

Can I update an existing pull request instead of creating a new one?

You can update an existing pull request by running the PR mode, which automatically detects your open request, stages relevant newly modified files, and updates the active branch and commit rather than opening a duplicate request.