Add blog-release-series skill (capture this week's lessons)#5134
Merged
Conversation
Captures the workflow and editorial lessons from the 2026-05-29
release cycle so the next week's release post + daily follow-ups
ship as a single batch PR rather than as a stack of sibling PRs
that each edit the previous post's wrap-up to add a forward link.
The skill covers:
- Recommended PR structure (one PR per release week, every post as
a separate .md, every per-post asset under static/blog/<slug>/).
- Front-matter conventions (quoted titles when they contain a
colon, slug == filename == url, feed_html mirrors description).
- Cross-post linking pattern (use "tomorrow's post" / "yesterday's
post" so a schedule shift doesn't require editing every
reference; sketch of a Hugo partial that would replace the
hand-written links entirely if the next batch wants it).
- Hugo preview workflow: local `hugo server --buildFuture` and the
Cloudflare PR preview URL the website-docs.yml workflow already
posts on every PR.
- Screenshot conventions: reuse the existing test fixtures under
scripts/{ios,android,javase}/screenshots*/ rather than asking for
fresh captures; a worked PIL crop + downscale example.
- Animated-GIF recipe from the 2026-06-01 codegen post (crop the
6-cell grid, mask labels, interpolate, share palette, 60ms / frame
loop), preserved in an appendix.
- Mermaid shortcode usage + the partialCached gotcha that drove the
inline loader.
- Editorial rules from reviewer feedback: no em-dashes, no first-
person "I", no "knob"/"deep dive"/AI tropes, build hints written
without codename1.arg. prefix, don't disparage the build cloud,
cloud handles the iOS build (no local Mac needed for cloud-built
iOS apps), no half-shipped features, real screenshots over ASCII,
bind examples must include the form, ML-Kit-style multi-cn1lib
coverage as per-cn1lib subsections, API-key handling rules, etc.
- Pre-merge checklist mapping each editorial rule to a grep command
or preview-URL spot-check.
The skill lives under skills/ alongside the existing
developer-guide-vale and ios-cn1ss-xcode-debug skills, with a
matching agents/openai.yaml interface block.
Contributor
✅ Continuous Quality ReportTest & Coverage
Static Analysis
Generated automatically by the PR CI workflow. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
skills/blog-release-series/to capture the workflow and editorial lessons from the 2026-05-29 release cycle so the next release week's posts ship as a single batch PR instead of as a chain of sibling PRs that each edit the previous post's wrap-up.Why
This week's cycle (intro #5074 already merged; workflow #5086 merged; platform APIs #5087 and codegen #5088 in review) shipped as stacked PRs. Every follow-up needed to:
git rebase --onto <merged-commit>after each merge to skip the squash-merged history.That pattern produced repeated merge conflicts and required multiple force-pushes per follow-up. The skill recommends moving to one batch PR per week, with all posts dated for their publish day and
HUGO_BUILD_FUTURE=true(already wired intowebsite-docs.ymlforpull_requestevents) rendering them on the Cloudflare preview URL while the live site keeps them hidden until their date.What's in the skill
tomorrow's post/yesterday's post); sketch of a Hugonext / previouspartial that would replace hand-written links entirely.hugo server --buildFuture; the Cloudflare preview URL).scripts/{ios,android,javase}/screenshots*/and a PIL crop / downscale example.partialCachedgotcha that drove the inline-loader pattern.codename1.arg., don't disparage the build cloud, cloud handles iOS builds so no local Mac is required, no half-shipped features, screenshots over ASCII, bind examples must show the form, ML-Kit-style per-cn1lib subsections, API-key handling rules).grepcommand or preview spot-check.Files
skills/blog-release-series/SKILL.md— the skill content.skills/blog-release-series/agents/openai.yaml— interface block matching the existingdeveloper-guide-valeandios-cn1ss-xcode-debugskills.Test plan
skills/.grepcommands are runnable against a sample post (em-dash check, first-person check,codename1.arg.check).