- 📁 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.
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/.
Increment the package version, commit the release, create a matching version tag, and push main plus the tag. Use when releasing this repo, publishing the package, bumping the version, tagging a release, or when the user asks to "release", "bump ver", "tag", or "push tags".
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.
Tend release workflow. Use when user asks to "do a release", "release a new version", "cut a release", or wants to publish a new version to PyPI.
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.
Manages CHANGELOG.md entries following Keep a Changelog format. Use when adding changelog entries, documenting changes, updating release notes, or preparing for a release. Triggers on terms like "changelog", "document changes", "release notes", "what changed".
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.
- 📁 tools/
- 📁 workflows/
- 📄 SKILL.md
Automate the full release workflow for syllago. USE WHEN creating a release OR tagging a version OR bumping VERSION OR publishing to GitHub releases.
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.
Bump version, update CHANGELOG, package the VSIX, publish to Open VSX and VS Code Marketplace, then commit and tag. Invoke via /publish [patch|minor|major] — default patch.
Use when the user wants a changelog, release notes, or asks what changed since the last release.
