skills.rest
cofade
cofadeCOMMUNITY
Explore all skills by this author →
GitHub

ogp-change-control

Manage change control processes in Open Garden Planner projects.

16|2|Updated Jan 24, 2026
Search Tags:#project management#version control#CI/CD#change control#release process
One-click install
npx skills add https://github.com/cofade/open-garden-planner --skill ogp-change-control
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ogp-change-control
Source: https://github.com/cofade/open-garden-planner/tree/main/.claude/skills/ogp-change-control
Command: npx skills add https://github.com/cofade/open-garden-planner --skill ogp-change-control

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures proper change control in Open Garden Planner projects, guiding users through the process of making changes, classifying them, and passing through the necessary gates.

Core Features & Use Cases

  • Change Classification: Classify changes as User Stories, Bug Fixes, or Chores, and manage them accordingly.
  • Non-Negotiable Gates: Follow non-negotiable rules for version control, PR creation, and release processes.
  • Integration Testing: Mandate integration testing and internationalization for every change.
  • Version Sync Protocol: Automate version synchronization after every CI release.
  • Release Pipeline: Manage the release pipeline with specific workflows for merging and publishing releases.

Quick Start

Use the ogp-change-control skill to check the status of a change and ensure it follows the proper process before branching or merging.

Frequently Asked Questions about ogp-change-control

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

FAQPage Schema
How do I manage change control for CI/CD release pipelines?▼

Change control for CI/CD release pipelines is managed by classifying changes, enforcing non-negotiable gates for PR creation, and automating version synchronization after every release.

What is the process for classifying changes in version control?▼

Classifying changes in version control involves categorizing them as User Stories, Bug Fixes, or Chores, then managing them through mandatory integration testing and specific release workflows.

How do I automate version synchronization after a CI release?▼

Version synchronization after a CI release is automated through a specific protocol that updates version numbers seamlessly once the release pipeline completes its merging and publishing workflows.

Do I need integration testing for every change in the release process?▼

Integration testing is mandated for every change in the release process. The change control protocol requires passing integration testing and internationalization checks as non-negotiable gates.

What are the non-negotiable gates for project PR creation?▼

Non-negotiable gates for PR creation include strict version control practices, mandatory integration testing, and internationalization checks before any changes can be merged or published.

When do I need to follow a version sync protocol in project management?▼

A version sync protocol is needed in project management immediately after every CI release to ensure all version numbers are accurately updated across the codebase before further changes are introduced.

Related Skills

Explore More Software Engineering Skills→
Extremez-SuryaExtremez-Surya

release

Automate the release process for vercel-plugin with gates, version bump, artifacts, commit, and push.

Community
Advanced
potetopoteto
218

deploy

Deployments orchestrated efficiently and securely.

Community
Intermediate
danieldev24danieldev24

ci-cd-and-automation

Automates CI/CD pipeline setup and quality gates for code verification.

Community
Advanced
myeohVmzrka92myeohVmzrka92

deployment-git

Coordinate PyPI publishing, version bumps, and Git release workflows.

Community
Advanced