skills.rest
DaFum
DaFumCOMMUNITY
Explore all skills by this author →
GitHub

change-plan-conventional-commits

Generate a change plan with conventional commits and a PR checklist from a request.

1|Updated Jan 6, 2026
Search Tags:#git#workflow#planning#pull-request#conventional-commits#risk-analysis#commit-messages
One-click install
npx skills add https://github.com/DaFum/neurotoxic-game --skill change-plan-conventional-commits
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change-plan-conventional-commits
Source: https://github.com/DaFum/neurotoxic-game/tree/main/.agents/skills/change-plan-conventional-commits
Command: npx skills add https://github.com/DaFum/neurotoxic-game --skill change-plan-conventional-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Concise change planning helps teams identify scope, risks, and impact, reducing miscommunication and review cycles.

Core Features & Use Cases

  • Generate a concise change plan from a request, outlining scope, risks, and implementation steps.
  • Propose Conventional Commit messages (feat, fix, refactor, docs) and a PR checklist to streamline reviews.
  • Provide a repeatable workflow for planning, review, and release coordination across small and large changes.

Quick Start

Provide a concise change plan with recommended conventional commits and a PR checklist for the requested work.

Frequently Asked Questions about change-plan-conventional-commits

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

FAQPage Schema
How do I plan git changes with conventional commit messages?▼

To plan git changes, this process summarizes the requested change, maps it to affected areas, outlines implementation steps, and drafts conventional commit messages with a PR checklist to streamline reviews.

What is the best way to structure a pull request checklist for risk analysis?▼

A pull request checklist for risk analysis identifies scope and impact, reducing miscommunication and review cycles by outlining validation checkpoints and proposing policy-aligned review items.

How do I generate conventional commits for a repository change plan?▼

Generating conventional commits for a change plan involves mapping the requested work to affected areas, outlining steps with validation checkpoints, and proposing feat, fix, refactor, or docs messages.

Can I use this change planning workflow for both small and large repository updates?▼

Yes, this change planning workflow provides a repeatable process for planning, review, and release coordination, accommodating both small and large repository updates with concise commit messages.

Why does my team need a conventional commit change plan before opening a pull request?▼

A conventional commit change plan reduces miscommunication and review cycles by identifying scope, risks, and impact upfront, ensuring the pull request aligns with team policies before implementation.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-baseline

Generate baseline-spec.md and current-state.md from repository analysis.

Community
Advanced
hyperlisthyperlist
271

git-workflow

Enforce Git branching, commit, and pull request standards with automated staging.

Community
Intermediate
gautam-achieveaigautam-achieveai
2

clean-builds

Automates code quality tools and package version validation in .NET projects.

Community
Advanced
ss49919201ss49919201

git-add-commit

Stage git changes and generate commit messages from diffs.

Community
Basic