Do wdr release

Skill d-oit/do-web-doc-resolver/.agents/skills/do-wdr-release

LLM-ready web documentation resolver: Python cascade skill + web + Rust CLI (wdr) with semantic cache, multi-provider routing, and quality synthesis

Install

npx -y skills add d-oit/do-web-doc-resolver --skill do-wdr-release

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Manage releases, versioning, changelogs, and GitHub releases. Use when creating releases, bumping versions, generating changelogs, creating tags, or managing the release workflow. Combines Git and GitHub best practices for professional releases.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, as published. Nobody here has run it

WDR Release Skill

Automated release management with Git and GitHub best practices.

When to use this skill

Activate this skill when you need to:

Create a new release (major/minor/patch)
Bump version numbers
Generate changelogs from commits
Create Git tags
Create GitHub releases
Automate release workflows
Capture release screenshots
Manage pre-release versions

Quick Start

Patch Release (0.1.0 → 0.1.1)

./scripts/release.sh patch

Minor Release (0.1.1 → 0.2.0)

./scripts/release.sh minor

Major Release (0.2.0 → 1.0.0)

./scripts/release.sh major

With Version Number

./scripts/release.sh 1.2.3

Release Workflow

IMPORTANT: This repo has a CI/CD release workflow (.github/workflows/release.yml) that automatically builds cross-platform binaries and creates the GitHub release when a v*.*.* tag is pushed. Do NOT use gh release create manually — it creates an incomplete release without binaries.

1. Prepare Release

# Ensure clean working directory
git status

# Run tests
./scripts/quality_gate.sh

2. Bump Version

# Update version in all files
python scripts/sync_versions.py --set $VERSION

3. Commit & Tag

git add -A
git commit -m "chore(release): v0.2.0"
git tag -a v0.2.0 -m "Release v0.2.0"
git push origin main --tags

4. Wait for CI/CD

The tag push triggers .github/workflows/release.yml which:

Runs Python and Rust test suites
Builds binaries for Linux, macOS, and Windows
Generates build attestations
Extracts changelog section from CHANGELOG.md
Creates GitHub release with binaries and install instructions

Monitor progress: gh run list --workflow=release.yml

References

Topic	File
Commit format & types	references/conventional-commits.md
Version bumping & sync	references/version-bumping.md
Changelog generation	references/changelog-format.md
CI/CD & pre-commit hooks	references/automation.md
Git & GitHub commands	references/commands-reference.md

Related Skills

do-wdr-assets: Screenshot capture
do-wdr-cli: Rust CLI
do-web-doc-resolver: Python resolver