pf-release_skill

This skill guides and automates the version release flow for PF projects, from changeset creation to deployment and release notes.
  • TypeScript

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill pluxity/pf-frontend --skill pf-release

  • SKILL.md5.6 KB

Overview

This skill documents and automates the PF DEV mono-repo release flow for versioning, tagging, and deployment. It guides maintainers through checks, changeset creation, bumping versions, generating Git tags, deploying, and publishing release notes. Designed for TypeScript monorepos managed with pnpm, Turbo, Changesets, and GitHub Actions.

How this skill works

It inspects repository state and runs the documented steps: confirm main branch and CI status, create a changeset, run pnpm bump and pnpm tag, commit and push tags selectively, and trigger or verify deployments. The skill enforces required checks like build/lint, user approval before pushing tags, and package whitelist for tagging. It also helps compose GitHub Release notes and rollback commands.

When to use it

  • Preparing a scheduled or hotfix release for PF DEV mono-repo
  • After changes are merged to main and all CI checks pass
  • When creating or updating package versions and Git tags
  • Before triggering automated production deployments
  • When drafting GitHub Release notes and publishing them

Best practices

  • Always update and test main locally: git checkout main && git pull before starting
  • Run build and lint (pnpm build, pnpm lint) and validate staging tests before tagging
  • Create a Changeset (pnpm changeset) and review .changeset/*.md before bumping versions
  • Commit version changes with issue number and use explicit tag pushes (do not use --follow-tags)
  • Require explicit user approval before pushing tags and ensure only whitelisted packages are tagged

Example use cases

  • Minor feature release: create changeset, pnpm bump, pnpm tag, push specified package tags, verify GH Actions run, publish GitHub Release
  • Patch hotfix: apply fix on main, run pnpm changeset for patch, bump, tag single package, push after approval, deploy to production
  • Staging-only deployment: bypass auto-deploy by running pnpm turbo build:staging --filter=app and manual SCP or script deployment
  • Rollback scenario: revert last commit, reinstall, rebuild and push revert to quickly undo a bad release

FAQ

Only specific packages are tagged and released: @pf-dev/ui, @pf-dev/map, @pf-dev/three, @pf-dev/cctv, @pf-dev/services. Others are excluded.

Can I push all tags with --follow-tags?

No. Do not use --follow-tags. Push only the release tags explicitly and after user approval.

How do I prepare release notes?

Use gh release create with a detailed notes string including What's New, Features, Bug Fixes, Breaking Changes, and an Upgrade Guide. Alternatively draft the release in GitHub Releases UI.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
pf-release skill by pluxity/pf-frontend | VeilStrat