- 📁 agents/
- 📁 references/
- 📄 SKILL.md
Publish peta-core releases from origin/main by preparing a detached temporary release workspace, generating English GitHub release notes, pushing Docker images, tagging the release, and publishing the GitHub release. Use when Codex is asked to release peta-core, bump the next patch version, publish a specific peta-core version, resume a prepared peta-core release, or clean up an abandoned prepared release workspace.
Create a new tagged npm release (patch/minor/major). Use when the user asks to release, publish, bump version, or cut a new version. Triggers on: release, publish, bump, version, tag.
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
Prepare and publish a new version of the waza azd extension.
Use the ClawHub CLI to search, install, update, and publish agent skills from clawhub.com. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders.
Scan, harden, sign, and verify release artifacts with ReleaseGuard — the artifact policy engine for dist/ and release/ outputs.
Implement features in the Edictum OSS core (src/edictum/). Use when the task touches pipeline, adapters, YAML engine, CLI, audit, envelope, or session. Core NEVER imports from ee/.
- 📁 evals/
- 📁 references/
- 📄 skill.js
- 📄 SKILL.md
Kuaifa (快发) — publish Markdown articles to WeChat Official Accounts via the kuaifa CLI. Use this skill whenever the user wants to publish an article to WeChat, publish image messages, manage kuaifa configuration or templates, or mentions '快发', 'kuaifa', 'publish to WeChat', '发布公众号', '微信发布', '发文章'. Also trigger when the user has a Markdown file and wants to distribute it to WeChat, or asks about WeChat article formatting and themes.
Manage Hathor wallet-lib release process. Use when initiating a release (PR from master to release branch) or bumping version (minor/patch/major). Handles PR creation with proper templates, reviewer assignment, labels, and GitHub project integration.
Release preparation and publish workflow: run tests, bump version, tag, push, and create a GitHub release (and update Homebrew formula if present). Use when asked to cut a release, bump version, create tags, or publish a release.
Release workflow for anna Go CLI project. Create releases with semantic versioned tags, update changelog, and trigger automated CI/CD builds. Use when the user asks to "release", "create a release", "tag a version", "update changelog", "prepare release", "cut a release", or discusses versioning and release artifacts. --- # Release ## Tag Format Use semantic versioning with `v` prefix: `v0.1.0`, `v1.0.0`, `v1.2.3-rc.1`. GoReleaser auto-detects pre-release suffixes (`-rc.1`, `-beta.1`). ## Release Flow 1. Update `docs/content/docs/changelog.mdx` (see below) 2. Commit: `📝 docs: Update CHANGELOG for vX.Y.Z` 3. Tag: `git tag vX.Y.Z` 4. Push: `git push origin main --tags` 5. CI triggers `.github/workflows/release.yml` → GoReleaser binaries + Docker images ## Update Changelog The changelog lives at `docs/content/docs/changelog.mdx` (rendered on the docs site). It has YAML frontmatter — preserve it when editing. Only modify content below the `---` block.
Publish this repository to npm as TeamCopilot after confirming the release version in package.json. Use this when the user wants to dry-run, verify, or publish a new npm release for this repo.
