docs: point create-prs-with-gh at the writing guide's PR section #31

Closed
jercik wants to merge 1 commit from docs/point-gh-skill-at-writing-guide into main
Owner

Finishes the fold in #29 by pointing create-prs-with-gh at the human-facing-writing-style Pull requests section, closing the routing gap #29's reviews flagged four times.

Finishes the fold in #29 by pointing `create-prs-with-gh` at the `human-facing-writing-style` Pull requests section, closing the routing gap #29's reviews flagged four times.
docs: point create-prs-with-gh at the writing guide's PR section
Some checks failed
Node tests / node:test (pull_request) Successful in 9s
commit-msg / commitlint (pull_request) Successful in 18s
PR Review / Prepare immutable review tools (pull_request_target) Successful in 1m30s
PR Review / forgejo-review-approach-3 generator (pull_request_target) Failing after 38s
PR Review / forgejo-review-approach-smart-2 generator (pull_request_target) Failing after 45s
PR Review / forgejo-review-code-smart-2 generator (pull_request_target) Failing after 47s
PR Review / forgejo-review-approach-smart-1 generator (pull_request_target) Successful in 1m25s
PR Review / forgejo-review-code-smart-1 generator (pull_request_target) Successful in 1m36s
PR Review / Dispatch and observe exact review writers (pull_request_target) Failing after 1m57s
4cf00aef44
forgejo-actions left a comment

Approach review: The approach is right and needs no alternative.

The change adds one routing sentence to skills/create-prs-with-gh/SKILL.md, delegating content guidance to human-facing-writing-style while the skill keeps its own narrow scope (shell quoting for gh body flags). Three things make this the correct shape:

  • It reuses the repository's established cross-skill idiom rather than inventing one. skills/verify-readme/SKILL.md:10 already reads "This skill covers what belongs in a README ... invoke the human-facing-writing-style skill", and the new line follows the same scope-then-delegate pattern.
  • The referenced target exists and is the right anchor: human-facing-writing-style has a ## Pull requests section covering titles, body, and what gets cut, so the pointer resolves to real content rather than a dangling reference.
  • The obvious alternative — copying title/body guidance into create-prs-with-gh — would duplicate a section that already has one owner and would drift. A prose pointer keeps a single source of truth, which matters more here because both skills are delivered independently per run.

Placement directly under the Goal line, before # Reference, means the delegation is read before the mechanics, which is the order a reader needs it in. No maintenance or scaling concern.

Approach review by Claude Code Opus (opus)

**Approach review:** The approach is right and needs no alternative. The change adds one routing sentence to `skills/create-prs-with-gh/SKILL.md`, delegating content guidance to `human-facing-writing-style` while the skill keeps its own narrow scope (shell quoting for `gh` body flags). Three things make this the correct shape: - It reuses the repository's established cross-skill idiom rather than inventing one. `skills/verify-readme/SKILL.md:10` already reads "This skill covers **what** belongs in a README ... invoke the `human-facing-writing-style` skill", and the new line follows the same scope-then-delegate pattern. - The referenced target exists and is the right anchor: `human-facing-writing-style` has a `## Pull requests` section covering titles, body, and what gets cut, so the pointer resolves to real content rather than a dangling reference. - The obvious alternative — copying title/body guidance into `create-prs-with-gh` — would duplicate a section that already has one owner and would drift. A prose pointer keeps a single source of truth, which matters more here because both skills are delivered independently per run. Placement directly under the Goal line, before `# Reference`, means the delegation is read before the mechanics, which is the order a reader needs it in. No maintenance or scaling concern. _Approach review by Claude Code Opus (opus)_ <!-- axrecipe-review:v1:eyJzY2hlbWFWZXJzaW9uIjoxLCJzdGF0ZSI6InB1Ymxpc2hlZCIsInJlcG9zaXRvcnkiOiJqNGstb3NzL2FnZW50LXNraWxscyIsIm51bWJlciI6IjMxIiwiaGVhZFNoYSI6IjRjZjAwYWVmNDRjMjYzN2UzYjc0YmRhYjM1YTBlYzJjNGY4MmJjODQiLCJzbG90IjoiZm9yZ2Vqby1yZXZpZXctYXBwcm9hY2gtc21hcnQtMSIsInNvdXJjZVdvcmtmbG93UnVuSWQiOiIxNjM2NyIsInNvdXJjZUdlbmVyYXRvckF0dGVtcHQiOiIxIiwicmVzdWx0SWQiOiI2ZTYxZjQ2Ny03MDQzLTQ4YjctOGY4Mi1kMzdjMGU3OTllMzMifQ== -->
forgejo-actions left a comment

Summary: No actionable issues found.

Single-sentence docs addition to skills/create-prs-with-gh/SKILL.md. Verified against the working tree:

  • The referenced skill exists at skills/human-facing-writing-style/SKILL.md, and its ## Pull requests section (line 267) covers exactly what the pointer promises — title shapes under ### Titles and body structure under ### Body.
  • The section name in the prose ("Pull requests") matches the heading verbatim, so the pointer will not dangle.
  • The wording follows the existing cross-reference convention in skills/verify-readme/SKILL.md:10 ("invoke the human-facing-writing-style skill"), keeping the delegation idiom consistent across the estate.
  • Both skills' frontmatter declare a "draft a PR description" trigger; the new sentence is what disambiguates them, which is the routing gap the PR set out to close.

No frontmatter, layout, or axskills delivery contract is touched, so nothing in the source's skills/<name>/SKILL.md structure is affected.

Code review by Claude Code Opus (opus)

**Summary:** No actionable issues found. Single-sentence docs addition to `skills/create-prs-with-gh/SKILL.md`. Verified against the working tree: - The referenced skill exists at `skills/human-facing-writing-style/SKILL.md`, and its `## Pull requests` section (line 267) covers exactly what the pointer promises — title shapes under `### Titles` and body structure under `### Body`. - The section name in the prose ("Pull requests") matches the heading verbatim, so the pointer will not dangle. - The wording follows the existing cross-reference convention in `skills/verify-readme/SKILL.md:10` ("invoke the `human-facing-writing-style` skill"), keeping the delegation idiom consistent across the estate. - Both skills' frontmatter declare a "draft a PR description" trigger; the new sentence is what disambiguates them, which is the routing gap the PR set out to close. No frontmatter, layout, or `axskills` delivery contract is touched, so nothing in the source's `skills/<name>/SKILL.md` structure is affected. _Code review by Claude Code Opus (opus)_ <!-- axrecipe-review:v1:eyJzY2hlbWFWZXJzaW9uIjoxLCJzdGF0ZSI6InB1Ymxpc2hlZCIsInJlcG9zaXRvcnkiOiJqNGstb3NzL2FnZW50LXNraWxscyIsIm51bWJlciI6IjMxIiwiaGVhZFNoYSI6IjRjZjAwYWVmNDRjMjYzN2UzYjc0YmRhYjM1YTBlYzJjNGY4MmJjODQiLCJzbG90IjoiZm9yZ2Vqby1yZXZpZXctY29kZS1zbWFydC0xIiwic291cmNlV29ya2Zsb3dSdW5JZCI6IjE2MzY3Iiwic291cmNlR2VuZXJhdG9yQXR0ZW1wdCI6IjEiLCJyZXN1bHRJZCI6IjQyMGIzMWNmLTc3ODEtNDZjMy1iZjRiLWVjOTM5Y2YzMzhhYiJ9 -->
Author
Owner

Closing unmerged: the estate triage decided to delete create-prs-with-gh rather than point it at the writing guide. Superseded by #32.

Closing unmerged: the estate triage decided to delete `create-prs-with-gh` rather than point it at the writing guide. Superseded by #32.
jercik closed this pull request 2026-08-04 15:35:15 +00:00
Some checks failed
Node tests / node:test (pull_request) Successful in 9s
commit-msg / commitlint (pull_request) Successful in 18s
PR Review / Prepare immutable review tools (pull_request_target) Successful in 1m30s
PR Review / forgejo-review-approach-3 generator (pull_request_target) Failing after 38s
PR Review / forgejo-review-approach-smart-2 generator (pull_request_target) Failing after 45s
PR Review / forgejo-review-code-smart-2 generator (pull_request_target) Failing after 47s
PR Review / forgejo-review-approach-smart-1 generator (pull_request_target) Successful in 1m25s
PR Review / forgejo-review-code-smart-1 generator (pull_request_target) Successful in 1m36s
PR Review / Dispatch and observe exact review writers (pull_request_target) Failing after 1m57s

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
j4k-oss/agent-skills!31
No description provided.