Skip to content

docs(skills): improve drafting skills from signal log patterns 2026-06-29#266

Open
rachaelrenk wants to merge 8 commits into
mainfrom
docs/improve-drafting-skills-2026-06-29
Open

docs(skills): improve drafting skills from signal log patterns 2026-06-29#266
rachaelrenk wants to merge 8 commits into
mainfrom
docs/improve-drafting-skills-2026-06-29

Conversation

@rachaelrenk

@rachaelrenk rachaelrenk commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Monthly improve-drafting-skills outer-loop run for 2026-06-29. Reads the last 30 days of signal data, identifies recurring drafting errors, and applies targeted, additive edits to the drafting skills.

Patterns addressed

Both edits land in draft_docs/SKILL.md step 6.5 (Critical formatting rules), the cross-cutting "frequently violated" list read on every drafting run.

Improvement targets

  • .agents/skills/draft_docs/SKILL.md — two additive bullets in step 6.5.
  • .agents/logs/human_review_feedback.jsonl — 9 collected human-feedback records from the Step B GitHub collection (folded into this PR because main is branch-protected and a direct push was rejected).

Patterns reviewed but not acted on

Signal sources note

  • Step A (Oz run artifacts): No [SIGNAL:style-lint] or [SIGNAL:pr-review] markers were emitted in the past 30 days. The only drafting runs (draft_docs) targeted the archived warpdotdev/gitbook repo and produced no markers and no PRs. No review-docs-pr runs occurred.
  • Step B (GitHub): Primary signal this cycle. Bot reviews (oz-for-oss[bot], etc.) were filtered out per the security boundary; only non-bot member feedback was used.

Open questions for human review

  • Should the error-code-embedding pattern (PR docs: crosslink API error references #166) be acted on now despite being a single-PR signal, given how explicitly a reviewer stated it? Left out this cycle to respect thresholds.

Infrastructure fix (added during human review)

The open question about signal marker retrieval was investigated and resolved. oz run get (without flags) returns only the brief RunItem.status_message field — not conversation content or shell stdout. Markers printed via echo in a shell command were invisible to the improve-drafting-skills collector.

Fix (3 files):

  • draft_docs/SKILL.md step 8 — emit [SIGNAL:style-lint] as agent text output (part of the agent's own message), not via shell echo. Agent text appears as a TextContentBlock in the conversation and is retrievable via oz run get --conversation.
  • review-docs-pr/SKILL.md — same fix for [SIGNAL:pr-review].
  • improve-drafting-skills/SKILL.md Step A — updated retrieval to use oz run get --conversation with a precise jq command that recursively traverses the steps[].messages[].content[] response structure. Also fixed an incorrect JSON path (messages[]steps[].messages[]) and added a concrete jq example.

Conversation: https://app.warp.dev/conversation/d8fc79d6-5723-42f3-a3d5-cc68a96b28a6
Run: https://oz.warp.dev/runs/019f1452-d491-7efc-95fb-d08418579969

This PR was generated with Oz.

oz-agent added 2 commits June 29, 2026 17:11
…2026-06-29

Co-Authored-By: Oz <oz-agent@warp.dev>
…6-29

Add two additive formatting rules to draft_docs step 6.5, both backed by
recurring human review feedback on agent-authored PRs:
- Descriptive, specific headings (PRs #143, #189)
- Tables/parallel bullets for comparison and reference data (PRs #143, #160, #166)

Co-Authored-By: Oz <oz-agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label Jun 29, 2026
@vercel

vercel Bot commented Jun 29, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jul 1, 2026 7:25pm

Request Review

@rachaelrenk rachaelrenk self-assigned this Jun 29, 2026
@rachaelrenk rachaelrenk marked this pull request as ready for review June 29, 2026 21:13
@oz-for-oss

oz-for-oss Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

@rachaelrenk

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@oz-for-oss oz-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This PR adds the June 29 drafting-skill improvement signal log and updates draft_docs critical formatting guidance with two additive rules for specific headings and comparison/reference-data structure.

Concerns

  • No blocking correctness, security, or spec-alignment concerns found in the annotated diff. spec_context.md reports that no approved or repository spec context was available for this PR.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

oz run get (no flags) returns only RunItem.status_message — a brief
status text — not full conversation content or shell stdout. Markers
printed via echo were invisible to the improve-drafting-skills
collector.

Fix: emit [SIGNAL:*] markers as agent text output (TextContentBlock)
rather than via shell echo, and update the collector to use
oz run get --conversation to scan assistant messages. Also fixes
the same pattern in review-docs-pr.

Co-Authored-By: Oz <oz-agent@warp.dev>
…afting-skills

oz run get --conversation returns {steps: [...]}, not {messages: [...]}.
Steps can be nested, so use recursive descent to reach all assistant
messages at any depth. Added a concrete jq example.

Co-Authored-By: Oz <oz-agent@warp.dev>
…ption

Adds check_pr_body.py, a reusable checker that detects repetition-loop degeneration (repeated spans, truncated inline code) and missing/duplicate headings in a PR body before it is submitted. Wires it into create_pr (create + safe additive-edit flows) and improve-drafting-skills Step 7.

Co-Authored-By: Oz <oz-agent@warp.dev>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants