V0.10.2/service update

AGENTS.md

@@ -199,7 +199,7 @@ Never set or override `git user.name`, `git user.email`, or `alias.bot` in the *
 Agents must never commit code changes or push to remote repositories without explicit user approval. A direct commit request that includes `yolo` or `auto` is explicit approval for the current commit request; it authorizes the agent to complete that commit workflow in the same turn after the required checks pass.
 
 - **Commits**: Request confirmation from the user before staging and committing code unless the same explicit commit request includes `yolo` or `auto`. In that auto-approved case, present the plan as status information and continue directly to staging and committing; do not ask a second confirmation question or end with a pending plan. Required review, scope, identity, message-validation, and post-commit checks still apply.
-- **Remote Operations**: Do not push, pull, fetch, or interact with `origin` or any remote repository without explicit user instruction. These operations modify repository history and can cause data loss if performed unexpectedly.
+- **Remote Operations**: Do not push, pull, fetch, or interact with `origin` or any remote repository without explicit user instruction. An explicit PR request authorizes read-only remote preparation; PR writes follow the PR Skill Routing approval boundary below.
 
 **Why:** Automatic commits can pollute history with incomplete work, debugging code, or unintended changes. Unexpected remote operations can overwrite or lose commits on shared branches. Never treat silence, urgency, or momentum as approval; `yolo` or `auto` counts as approval only when attached to the same explicit commit request.
 
@@ -209,6 +209,10 @@ When the user asks to commit or stage changes, write or review a commit message,
 
 Bare `yolo` or `auto` outside an explicit commit request does not invoke `git-visual-commits`. Likewise, those modifiers do not invoke `git-keep-a-changelog` unless the user explicitly requests a changelog or release-note output. Users can force deterministic CLI selection with `/git-visual-commits` when they do not want to rely on automatic skill selection.
 
+### PR Skill Routing
+
+When the user asks to create, open, make, or refresh a GitHub pull request, invoke `git-remote-pr` before remote PR operations. Normal requests inspect the complete committed `base...head` changeset, prepare a title/body and exact mutation preview, then require explicit approval before `git push` or PR writes. `yolo`/`auto` attached to that same explicit PR request authorizes those narrow writes after the preview is shown; bare `yolo`/`auto` does not invoke the skill. Existing PR descriptions are regenerated from the complete current changeset. Dirty worktrees are not auto-committed, and approval never authorizes force pushes or history rewriting. Commit requests remain with `git-visual-commits`; release-note requests remain with `git-remote-release`. `/git-remote-pr` can force deterministic selection where supported.
+
 ## Skill Creation
 
 Always use the `skill-creator` skill (by Anthropic) when creating new skills, modifying existing skills, or running evals. It enforces best practices for structure, description quality, testing, and progressive disclosure. Do not create or edit skills manually without invoking it first.
@@ -309,11 +313,11 @@ When committing changes to this repo, group by technology and logical purpose 
 - Template files (`.csproj`, `.yml`, `.cs`) get their own commit(s)
 - Documentation updates (`README.md`, `CONTRIBUTING.md`) get their own commit
 
-## Markdown Formatting
+## Markdown Prose Formatting
 
-All markdown files in this repository must use natural paragraph flow. Do not artificially break paragraphs at fixed column widths or insert hard line breaks within sentences. Paragraphs should flow as complete thoughts, allowing line wrapping to be determined by the reader's viewport or rendering engine, not by arbitrary character limits.
+Do not hard-wrap prose to a fixed column width. Keep paragraphs and Markdown list items on continuous natural lines regardless of their length. Do not insert line breaks merely to satisfy 80, 100, 120, or any other column-width limit; rely on editor soft wrapping for visual presentation. Insert physical line breaks only where Markdown structure requires them, such as between paragraphs, headings, list items, code blocks, and tables. When modifying existing Markdown, remove unnecessary hard wrapping from the prose you touch.
 
-**Why:** Natural paragraphs are more readable, easier to edit, and render correctly across all devices and markdown renderers. Artificially clipped paragraphs create maintenance friction and look awkward in source control diffs.
+**Why:** Natural paragraphs and list items are easier to read and edit, and they render consistently across Markdown viewers. Arbitrary line breaks create maintenance friction and noisy diffs.
 
 ## README Sync
 

CHANGELOG.md

@@ -4,6 +4,36 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.11.0] - 2026-09-24
+
+This is a minor release introducing `git-remote-pr`, a Git and GitHub CLI skill for managing GitHub pull requests from the complete committed branch comparison, establishing working-tree scratch isolation standards for all skills, and applying markdown prose formatting conventions across the skill documentation suite. The new skill brings deterministic evidence collection, safe push and assignment handling, post-write verification, and focused regression tests. Repository guidance clarifies where temporary artifacts belong, and skill documentation now follows consistent markdown formatting standards. The `agent-smith` skill is restructured around an operating model framework, with new capability references for agentic engineering patterns and automation, a dedicated validation test suite, and visual identification assets for all skills.
+
+### Added
+
+- `git-remote-pr`, a Git and GitHub CLI skill for preparing, reviewing, creating, and refreshing GitHub pull requests from the complete committed `base...head` changeset, with deterministic evidence collection (`prepare-pr.ps1`), safe push and assignment handling, post-write verification (`execute-pr.ps1`), plan generation and preview (`make-plan.ps1`), regression test suite, and PR routing guidance in AGENTS.md,
+- PR Skill Routing section in AGENTS.md documenting when and how `git-remote-pr` is invoked, its approval boundary, scope rules, and interaction with commit and release-note workflows,
+- Working-tree Scratch Isolation section in AGENTS.md establishing consistent practices for temporary artifacts, API responses, investigation notes, intermediate files, and eval fixtures, designating `.bot/<task>-workspace/` as the default inside the repository and allowing operating-system temp directories for items with no reason to sit nearby, and forbidding temporary git repos and test branches from becoming part of the working tree,
+- Markdown Prose Formatting standards section in AGENTS.md requiring prose paragraphs and list items to remain on continuous physical lines without arbitrary hard wrapping and relying on editor soft wrapping for visual presentation,
+- Updated README.md with `git-remote-pr` entry in the skills catalog, installation command, and a new "Why git-remote-pr?" community health section explaining the skill's purpose and boundaries,
+- Deterministic validation for `git-remote-pr` in `scripts/validate-skill-templates.ps1` asserting that PR skill routing and deterministic workflow remain integrated across AGENTS.md, README.md, SKILL.md, and bundled scripts,
+- New eval case for `git-visual-commits` testing working-tree scratch isolation principles,
+- Markdown prose formatting applied consistently across 12 skill SKILL.md files, reference documents, and asset templates, including agent-smith, dotnet-docfx-digest, dotnet-new-app-slnx, dotnet-new-lib-slnx, dotnet-segregated-assets, git-keep-a-changelog, git-nuget-readme, git-nuget-release-notes, git-remote-release, git-repo-digest, git-visual-commits, and git-visual-squash-summary,
+- Enhanced `git-visual-commits` scratch file isolation guidance with explicit pre-write requirements, temporary path verification, symlink and junction target checks, and forbidden pattern examples,
+- `agent-smith` skill restructured with operating model framework focus, clarifying durable software and agentic engineering decision orientation, updated descriptions emphasizing intent and trigger precision, and refactored guidance for skills across the portfolio,
+- Two new reference documents for `agent-smith`: `agentic-engineering.md` documenting patterns and principles for engineering autonomous agent systems, and `automation.md` covering automation boundaries, safety, and governance,
+- `test-agent-smith.ps1` deterministic validation test suite for `agent-smith` skill including conformance assertions, guidance validation, and reference coverage checks, integrated into `scripts/validate-skill-templates.ps1` for automated repository validation,
+- Hero images (`.jpg`) for eight skills providing visual identification and documentation rendering support: agent-smith, dotnet-benchmark, dotnet-docfx-digest, dotnet-new-app-slnx, dotnet-new-lib-slnx, dotnet-remote-testing, dotnet-segregated-assets, dotnet-test, and git-remote-pr,
+- Updated skill descriptions across the repository portfolio to emphasize operating model, trigger precision, and user intent following progressive-disclosure principles from the specification.
+
+### Changed
+
+- Repository-level guidance in AGENTS.md now includes markdown prose formatting standards and working-tree scratch isolation principles as core agent conventions,
+- README.md updated with markdown prose formatting guidance for skill authors, updated skills table with hero images and refined descriptions, and additional community health sections explaining repository standards,
+- `agent-smith` description and README catalog entry refactored to emphasize operating model for durable software and agentic engineering rather than comprehensive reference,
+- `scripts/validate-skill-templates.ps1` enhanced with validators for git-remote-pr integration, markdown formatting standards, working-tree scratch isolation across affected skills, and agent-smith skill validation,
+- `git-visual-commits` SKILL.md clarified with improved scratch file isolation requirements and pre-write verification procedures,
+- `git-keep-a-changelog` SKILL.md and evals updated for markdown formatting standards consistency.
+
 ## [0.10.1] - 2026-09-14
 
 This is a patch release that enhances `git-keep-a-changelog` with explicit dependency removal disclosure and improved pending-change handling for both committed and worktree edits, refactors `git-visual-squash-summary` to require complete coverage of all surviving changes and contributors, and adds deterministic GitHub API evidence collection to `git-remote-release`. The eval-runner infrastructure gains JSON property-lookup performance optimization and in-process result validation via composition mode. Repository guidance is expanded with scratch-file isolation practices and scheduler-performance documentation for local validation.
@@ -693,6 +723,7 @@ This is a minor release that introduces two complementary git workflow skills, e
 
 - Improved scaffold fidelity with hidden `.bot` asset preservation, explicit UTF-8 and BOM handling, and checks aimed at preventing mojibake or incomplete generated output.
 
+[0.11.0]: https://github.com/codebeltnet/agentic/compare/v0.10.1...v0.11.0
 [0.10.1]: https://github.com/codebeltnet/agentic/compare/v0.10.0...v0.10.1
 [0.10.0]: https://github.com/codebeltnet/agentic/compare/v0.9.1...v0.10.0
 [0.9.1]: https://github.com/codebeltnet/agentic/compare/v0.9.0...v0.9.1