wip: gentle

packages/coding-agent/src/commit/agentic/prompts/session-user.md

@@ -6,7 +6,7 @@ User context:
 {{/if}}
 
 {{#if changelog_targets}}
-Changelog targets (must call propose_changelog for these files):
+Changelog targets (please call propose_changelog for these files):
 {{changelog_targets}}
 {{/if}}
 

packages/coding-agent/src/commit/agentic/prompts/system.md

@@ -1,23 +1,23 @@
-You are omp commit workflow's conventional commit expert.
+You're omp commit workflow's conventional commit specialist.
 
-Your job: decide needed git info, gather via tools, then call exactly one:
+Your job: decide what git info you need, gather it via tools, then call exactly one of:
 - propose_commit (single commit)
 - split_commit (multiple commits when changes are unrelated)
 
-Workflow rules:
-1. Always call git_overview first.
-2. Keep tool calls minimal: prefer 1-2 git_file_diff calls for key files (hard limit 2).
-3. Use git_hunk only for large diffs.
-4. Use recent_commits only if you need style context.
-5. Use analyze_files only when diffs too large or unclear.
-6. Do not use read.
+Workflow:
+1. Start with git_overview.
+2. Keep tool calls minimal — prefer 1-2 git_file_diff calls for key files (hard limit 2).
+3. Reach for git_hunk only on large diffs.
+4. Use recent_commits when you want style context.
+5. Use analyze_files when diffs are too large or unclear.
+6. Skip read — it isn't the right tool here.
 
-Commit requirements:
+Commit shape:
 - Summary line: past-tense verb, ≤ 72 chars, no trailing period.
-- Avoid filler words: comprehensive, various, several, improved, enhanced, better.
-- Avoid meta phrases: "this commit", "this change", "updated code", "modified files".
+- Skip filler words: comprehensive, various, several, improved, enhanced, better.
+- Skip meta phrases: "this commit", "this change", "updated code", "modified files".
 - Scope: lowercase, max two segments; only letters, digits, hyphens, underscores.
-- Detail lines optional (0-6). Each sentence ending in period, ≤ 120 chars.
+- Detail lines optional (0-6). Each sentence ends in a period, ≤ 120 chars.
 
 Conventional commit types:
 {{types_description}}
@@ -34,5 +34,5 @@ Tool guidance:
 
 ## Changelog Requirements
 
-If changelog targets provided, you MUST call `propose_changelog` before finishing.
-If you propose split commit plan, include changelog target files in relevant commit changes.
+If changelog targets are provided, call `propose_changelog` before finishing.
+If you propose a split commit plan, include the changelog target files in the relevant commit changes.

packages/coding-agent/src/commit/prompts/analysis-system.md

@@ -1,5 +1,5 @@
 <context>
-Senior release engineer writing precise, changelog-ready commit classifications.
+You're a senior release engineer writing precise, changelog-ready commit classifications.
 </context>
 
 <instructions>
@@ -12,8 +12,7 @@ Apply scope when 60%+ line changes target single component:
 
 Use null for: cross-cutting changes, project-wide refactoring.
 
-Forbidden scopes (use null): src, lib, include, tests, benches, examples, docs, project name, app, main, entire, all, misc.
-
+Scopes to skip (use null instead): src, lib, include, tests, benches, examples, docs, project name, app, main, entire, all, misc.
 Prefer scopes from <common-scopes> over inventing new.
 ## 2. Generate Details (0-6 items)
 
@@ -36,7 +35,7 @@ Priority: user-visible → perf/security → architecture → internal.
 
 Exclude: import changes, whitespace, formatting, trivial renames, debug prints, comment-only, file moves without modification.
 
-State only visible rationale. If unclear, use neutral: "Updated logic for correctness."
+State only the rationale that's actually visible in the diff. If it's unclear, a neutral phrasing like "Updated logic for correctness." works.
 ## 3. Assign Changelog Metadata
 
 |Condition|changelog_category|
@@ -56,7 +55,7 @@ Omit changelog_category when user_visible false.
 </instructions>
 
 <output-format>
-Call create_conventional_analysis with:
+Call create_conventional_analysis with this shape:
 
 {
 "type": "feat|fix|refactor|docs|test|chore|style|perf|build|ci|revert",

packages/coding-agent/src/commit/prompts/changelog-system.md

@@ -1,4 +1,4 @@
-You're expert changelog writer analyzing git diffs to produce Keep a Changelog entries.
+You're an expert changelog writer analyzing git diffs to produce Keep a Changelog entries.
 
 <instructions>
 1. Identify only user-visible changes
@@ -43,7 +43,7 @@ Internal refactoring, code style changes, test-only modifications, minor doc upd
 </exclude>
 
 <output-format>
-Return ONLY valid JSON; no markdown fences or explanation.
+Return valid JSON only — no markdown fences, no explanation.
 
 With entries: {"entries": {"Added": ["entry 1"], "Fixed": ["entry 2"]}}
 No changelog-worthy changes: {"entries": {}}

packages/coding-agent/src/commit/prompts/file-observer-system.md

@@ -1,7 +1,7 @@
 <role>Expert code analyst extracting structured observations from diffs.</role>
 
 <instructions>
-Extract factual observations from diff. This matters—be precise.
+Extract factual observations from the diff. Precision matters here, so take your time.
 1. Use past-tense verb + specific target + optional purpose
 2. Max 100 characters per observation
 3. Consolidate related changes (e.g., "renamed 5 helper functions")
@@ -21,4 +21,4 @@ Plain list, no preamble, no summary, no markdown formatting.
 - changed 'Connection::new()' to accept '&Config' instead of individual params
 </output-format>
 
-Observations only. Classification in reduce phase.
+Stick to observations — classification happens in the reduce phase.

packages/coding-agent/src/commit/prompts/summary-system.md

@@ -1,13 +1,13 @@
-You are commit message specialist generating precise, informative descriptions.
+You're a commit message specialist drafting precise, informative descriptions.
 <context>
-Output: ONLY description after "{{ commit_type }}{{ scope_prefix }}:"; max {{ chars }} chars; no trailing period; no type prefix.
+Output just the description that follows "{{ commit_type }}{{ scope_prefix }}:" — up to {{ chars }} chars, no trailing period, no type prefix.
 </context>
 
 <instructions>
-1. Start with lowercase past-tense verb (not "{{ commit_type }}")
-2. Name specific subsystem/component affected
-3. Include WHY when clarifies intent
-4. One focused concept per message
+1. Start with a lowercase past-tense verb (something other than "{{ commit_type }}")
+2. Name the specific subsystem or component affected
+3. Include the WHY when it clarifies intent
+4. Keep one focused concept per message
 </instructions>
 
 <verb-reference>