Finish a release after `lerna publish` has run on `develop` (the "chore(root): Publish packages" commit is on develop, versions/tags/CHANGELOGs updated, packages pushed to npm). Does the two manual follow-up steps: (1) create a GitHub release per newly published package with notes taken from that package's CHANGELOG.md, and (2) fast-forward `master` to `develop`. Also strips any Co-Authored-By / tool trailers that leaked into a CHANGELOG. Use right after a successful publish; do NOT use to run the publish itself.
Verify local (uncommitted) assemble-lite changes by running a real Living Styleguide (LSG) build against a consumer project. Use when testing or verifying assemble-lite dependency bumps or changes to its render/glob/data/helper code before publishing. assemble-lite has no bin and is consumed transitively via @pro-vision/pv-stylemark, so the test injects the local package into the consumer's node_modules and runs `pv-stylemark prod`. The skill ALWAYS asks which consumer project to build — no project is hardcoded.
Verify local (uncommitted) pv-scripts changes by running a real build against a consumer project that uses pv-scripts. Use when testing or verifying pv-scripts dependency bumps, webpack-config/task changes, or any change under packages/pv-scripts before publishing. The skill ALWAYS asks which consumer project to build — no project is hardcoded.