wehub-resource-sync
e071084ebe
3.0 KiB
Act as DevRel for go-micro. Do these, in order.
COHERENCE AUDIT. Audit the public surface — README.md, internal/website/ (landing index.html + docs/), and the blog under internal/website/blog/ — for coherence with the North Star in .github/loop/NORTH_STAR.md (an agent harness and service framework; the services → agents → workflows lifecycle). Look for: places where README / website / docs contradict each other, are stale, or describe behavior that has since changed (cross-check against the code and recently merged PRs); whether the README is crisp and leads with the harness positioning; and one to three genuinely blog-worthy items from recently shipped work.
CHANGELOG UPKEEP (safe factual task — goes in the auto-merged PR). Keep CHANGELOG.md living, in Keep-a-Changelog format with newest content at the top under ## [Unreleased]. Enumerate PRs merged to master since the last update (gh pr list --state merged --base master --limit 60 --json number,title,mergedAt,labels) and add a concise, user-facing entry for each genuine change not yet recorded under the right ### Added / ### Changed / ### Fixed / ### Documentation subheading — SKIP internal loop/CI/priorities-refresh churn. If a new vX.Y.Z tag was cut since the last run (git fetch --tags --force), rename ## [Unreleased] to ## [X.Y.Z] - <Month YYYY> and open a fresh empty ## [Unreleased] above it. Do not invent entries.
CHANGELOG BLOG POST (blog voice — do NOT auto-merge). If, and only if, enough user-facing work has accumulated since the last changelog post to be worth reading (roughly a week's worth; not a near-empty post every day), draft a short "What's new in Go Micro" post as the next-numbered file in internal/website/blog/, mirroring the latest post's frontmatter and prev-nav, and add an entry at the top of internal/website/blog/index.html. Base it strictly on the CHANGELOG.
THEN: (A) post a findings report as a comment on this issue (#ISSUE) — what's aligned, what drifted, what you fixed, the CHANGELOG entries added, and whether you drafted a blog post (and why/why not). (B) Open ONE auto-merging PR for the SAFE factual work only — coherence/crispness fixes AND the CHANGELOG update (NOT brand/positioning rewrites, NOT the blog post): git switch -c codex/coherence-__ISSUE__, git push -u origin codex/coherence-__ISSUE__, gh pr create --base master --label codex --title "<title>" --body "<summary, Closes #__ISSUE__>", then gh pr merge --squash --auto --delete-branch. (C) If you drafted a changelog blog post, open it as a SEPARATE PR (codex/coherence-blog-__ISSUE__, title prefixed blog:) and do NOT enable auto-merge — leave it for the human. Same for any brand/positioning copy. Do not use the make_pr tool.