Web Design Consultant
I want you to act as a web design consultant. I will provide you with details related to an organization needing assistance designing or redeveloping their website, and your role is to suggest the mos...
Create a release following Git Flow strategy. Use when preparing a release, bumping version, creating release branch, or when user says "release", "bump version", "prepare release", "ship version".
Sign in to like and favorite skills
I want you to act as a web design consultant. I will provide you with details related to an organization needing assistance designing or redeveloping their website, and your role is to suggest the mos...
I want you to act as an accountant and come up with creative ways to manage finances. You'll need to consider budgeting, investment strategies and risk management when creating a financial plan for yo...
I want you to act as an IT Architect. I will provide some details about the functionality of an application or other digital product, and it will be your job to come up with ways to integrate it into...
This skill guides the release process following Git Flow with automated CI/CD.
develop ──▶ release/v{X.Y.Z} ──PR──▶ main ▲ │ │ ▼ │ (auto-release.yml) │ │ │ ▼ │ tag: v{X.Y.Z} │ │ │ ▼ │ (publish.yml) │ │ │ ▼ │ JSR publish │ │ └───────────── backmerge ◀──────────┘
git checkout develop git pull origin develop git status
Verify all features for this release are merged.
deno task ci
All tests must pass before proceeding.
Follow semantic versioning:
Check current version:
jq -r '.version' deno.json
git checkout -b release/v{NEW_VERSION}
Use the project's bump script:
bash scripts/bump_version.sh
Or manually update
deno.json:
# Edit deno.json version field
Add release notes under new version heading.
git add deno.json CHANGELOG.md git commit -m "chore: bump version to {NEW_VERSION}"
git push -u origin release/v{NEW_VERSION}
Create PR:
release/v{NEW_VERSION} → main
Important: PR must be from
release/* branch directly to main for auto-release to trigger.
When PR to main is merged:
auto-release.yml creates tag v{NEW_VERSION}publish.yml publishes to JSRAfter release is published, backmerge main to develop:
git checkout develop git pull origin develop git merge origin/main git push origin develop
This ensures develop has the version bump and CHANGELOG updates.
deno task ci passesdeno.json# Prepare git checkout develop git pull origin develop deno task ci # Create release git checkout -b release/v1.8.0 bash scripts/bump_version.sh # Edit CHANGELOG.md git add deno.json CHANGELOG.md git commit -m "chore: bump version to 1.8.0" git push -u origin release/v1.8.0 # Create PR via GitHub # release/v1.8.0 → main (triggers auto-release on merge) # After merge and JSR publish, sync develop git checkout develop git pull origin develop git merge origin/main git push origin develop
maindeno.json must match tagrelease/* branch merge to main