refining

Enforce change cohesion and generate commit messages and PR descriptions.

3|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/lidessen/moniro --skill refining
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refining
Source: https://github.com/lidessen/moniro/tree/main/skills/refining
Command: npx skills add https://github.com/lidessen/moniro --skill refining

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refining ensures code changes are cohesive and easy to review by validating cohesion, reducing mixed concerns, and producing clear commit messages and PR/MR descriptions.

Core Features & Use Cases

  • Cohesion checks: Split mixed concerns into focused changes that are independently verifiable.
  • Commit message generation: Produce concise, conventional-commits-style messages.
  • PR/MR description generation: Create reviewer-focused descriptions that explain intent and risk.
  • Use Case: Before submitting a PR, run refining to ensure changes are well-scoped and well-described.

Quick Start

Start the refining workflow when preparing changes for review, and use it to verify cohesion, generate a commit message, and prepare a PR description.

Frequently Asked Questions about refining

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

FAQPage Schema
How do I ensure my code changes are cohesive before submitting a PR?

To improve code reviewability, you can enforce change cohesion by splitting mixed concerns into focused, independently verifiable changes. This process ensures your code changes are cohesive and easy to review before submission.

How do I generate conventional commit messages for my staged changes?

You can generate concise, conventional-commits-style commit messages by applying a cohesion validation workflow during the commit process. This standardizes commit messages to accurately reflect scoped, focused changes.

What should a reviewer-focused PR description include?

A reviewer-focused PR description should explain the intent and risk of the changes. Generating these descriptions during PR creation streamlines reviewer feedback by providing clear context for the submitted changes.

Why does my pull request take too long to review?

Your pull request likely takes too long to review because it contains mixed concerns that reduce reviewability. Validating change cohesion and splitting the PR into focused changes streamlines the feedback process.

When do I need to validate change cohesion in my workflow?

You need to validate change cohesion during commits, code reviews, and PR creation. Applying this validation before submitting changes ensures they are well-scoped, well-described, and easy for reviewers to verify.

Can I split mixed concerns into focused changes automatically?

Yes, you can identify and split mixed concerns into focused changes that are independently verifiable. This process guides how changes are divided and described to improve overall reviewability before submission.