release
This skill orchestrates the complete release process for claude-code-viewer, from version specification through signed commit creation, tag management, and GitHub Actions workflow monitoring. It handles version bumps (patch, minor, major, beta, or explicit semver), validates preconditions like SSH signing config, and guides you through GitHub Release note cleanup and publishing.
release executes an end-to-end version bump, tagging, and GitHub publishing workflow for claude-code-viewer.
AI-generated summary based on this skill's SKILL.md
Install
d-kimuson/claude-code-viewer/release · repository language: TypeScript
git clone https://github.com/d-kimuson/claude-code-viewer
cp -r claude-code-viewer/.agents/skills/release ~/.claude/skills/releasenpx skillfed install d-kimuson/claude-code-viewer/releaseFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I release a new version of claude-code-viewer?
The release skill orchestrates the complete release process for claude-code-viewer, handling version bumps (patch, minor, major, beta, or explicit semver), creating signed commits and tags, and monitoring GitHub Actions workflow execution. You specify your desired version type or explicit semver, the skill validates your SSH signing configuration, and then guides you through GitHub Release note cleanup and publishing to finalize the release.
What version formats does release support?
The release skill for claude-code-viewer supports patch, minor, and major version bumps following semantic versioning, as well as beta releases and explicit semver specifications. You can release a patch fix, a minor version bump, a major version bump, beta versions like 0.8.0-beta.0, or specify an exact version number like 0.8.0 directly.
How does release handle signed commits and tags?
The release skill validates your SSH signing configuration as a precondition before proceeding. It manages the creation of signed commits and tags throughout the release process, ensuring your releases are cryptographically verified and secure. This signed release workflow is part of the end-to-end release automation for claude-code-viewer.
Can release automate GitHub Actions monitoring?
Yes, the release skill automates GitHub Actions monitoring and release workflow execution as part of its end-to-end release automation. It monitors the workflow as your release progresses, helping you track the release state and verify npm package publication without manual intervention.
What happens after the release workflow completes?
Once the release skill's GitHub Actions workflow completes, it guides you through GitHub Release note cleanup and publishing. You can review and polish the generated release notes before publishing them to GitHub Release, completing the full release process for claude-code-viewer.
SKILL.md
rendered from the published skill — quoted content, verbatim
claude-code-viewer Release
Use this skill to perform an end-to-end release for this repository.
Inputs
Interpret the user's argument as the release version spec:
patch,minor,major,beta- or an explicit semver such as
0.8.0/0.8.0-beta.0
If no version spec is present, ask the user which one to use.
Preconditions
- Work from the repository root.
- Inspect the current branch and working tree:
git branch --show-current
git status --short
- If there are unrelated uncommitted changes, stop and ask the user how to handle them.
- If release-related changes were just made, commit them before running release because
scripts/release.tsrequires a clean working tree. - The release script requires SSH signing config:
git config --get gpg.format
git config --get commit.gpgsign
git config --get tag.gpgsign
Expected values are
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.agents/skills/release/SKILL.md