mikker PR
Read the commit skill for guidance on describing changes and writing commits.
Flow
- Inspect repository instructions, status, diff, branch, and trunk.
- Verify the change. Commit only intended work, then push the branch.
- Create or update the PR with the format below.
Format
Title: Imperative change description.
Description:
<One imperative sentence.>
## TL;DR
<Brief summary.>
## Problem
<If applicable, one brief sentence covering the issue.>
## Desired outcome
<What we want.>
## Solution
<How we achieve it.>
## Context for agents
<Optional follow-up context, decisions, or discoveries.>
Keep the human-facing sections very short, plain, and product-level. Describe the resulting user experience, not implementation details. Mention the previous state only when it explains the problem, a decision, or other necessary context.
Omit Problem and Context for agents when unnecessary. Keep agent context minimal and clearly secondary to the human-facing description.