skills.rest
crissdiamond
crissdiamondCOMMUNITY
Explore all skills by this author →
GitHub

crisai-change-control

Classify code changes and enforce commit conventions in the crisAI repository.

Updated Apr 18, 2026
Search Tags:#code review#repository management#commit conventions#CI integration#change control
One-click install
npx skills add https://github.com/crissdiamond/crisAI --skill crisai-change-control
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: crisai-change-control
Source: https://github.com/crissdiamond/crisAI/tree/main/.claude/skills/crisai-change-control
Command: npx skills add https://github.com/crissdiamond/crisAI --skill crisai-change-control

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides comprehensive guidelines and automated checks to ensure adherence to change control and best practices within the crisAI repository.

Core Features & Use Cases

  • Change Classification: Automates classification of changes into registry edits, code changes, prompt edits, docs changes, and ADR-worthy updates.
  • Pre-Commit Checks: Offers a checklist to ensure all necessary checks are performed before committing code.
  • Commit Body Guidance: Assists in writing effective commit messages with detailed post-mortem information.
  • CI Integration: Integrates with the CI pipeline to enforce security and code quality standards.

Quick Start

To use the crisai-change-control skill, run the command: crisai-change-control.

Frequently Asked Questions about crisai-change-control

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

FAQPage Schema
How do I automate code change classification and enforce commit conventions in my repository?▼

Automating code change classification involves categorizing updates into registry edits, code changes, prompt edits, and docs changes. This process enforces commit conventions and CI checks to ensure repository operations adhere to change management best practices.

What is the best way to ensure pre-commit checks are completed before pushing code changes?▼

Ensuring pre-commit checks requires running a validation checklist before committing code. This verifies that security and code quality standards are met, preventing non-compliant changes from entering the CI pipeline.

How do I write effective commit messages with post-mortem information for change control?▼

Writing effective commit messages requires detailed post-mortem information documenting the change context. This Skill provides commit body guidance to ensure messages meet change control standards and document repository updates accurately.

Does CI integration enforce security and code quality standards for repository management?▼

CI integration enforces security and code quality standards by validating changes against pipeline checks. This ensures that committed code changes comply with repository best practices before they are merged.

Do I need a configured environment to run change control automation on the crisAI repository?▼

Yes, running change control automation requires access to the crisAI repository and a configured environment. This setup is necessary to execute automated checks, classify changes, and validate CI standards.

Related Skills

Explore More Software Engineering Skills→
JuanMS20JuanMS20

github-auth

Configure GitHub authentication for Hermes Agent using git, gh CLI, or SSH credentials.

Community
Intermediate
beomeodevbeomeodev

ms-essentials-review

Automate TRUST-5 compliant code reviews and Constitution-adherence checks in CI pipelines.

Community
Advanced
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced
crissdiamondcrissdiamond

crisai-validation-and-qa

Validate crisAI repository changes with pytest, ruff, mypy, and coverage analysis.

Community
Advanced