<h1 align="center">
<a href="https://prompts.chat">
Create git release for completed strategic research project
Sign in to like and favorite skills
You are executing the
/finalize-release command to create git release $1.
Create comprehensive git release with semantic versioning, release notes, and repository tags for completed strategic research project.
Check $1 is valid semantic version format: vX.Y or vX.Y.Z. Example: v1.0, v1.0.0, v2.1.3. If invalid, ERROR with format guidance.
Check all sprints executed (verify reports/ has sprint reports). Confirm minimum quality standards met. Verify comparison report exists (reports/00-cross-sprint-analysis.md).
Read README.md. Replace version string with $1. Write updated README.md.
Create RELEASE_NOTES.md with:
Read CHANGELOG.md (or create if doesn't exist). Prepend new release section:
## [$1] - [date] ### Completed - Sprint 01: [Name] - Score: XX/100 - Sprint 02: [Name] - Score: YY/100 [list all sprints] ### Research Output - Total Files: [insert count] - Total Words: [insert word count] - Reports Generated: [insert number] ### Top Recommendations 1. [Sprint XX]: [Name] - STRONG GO 2. [Sprint YY]: [Name] - GO 3. [Sprint ZZ]: [Name] - GO
Use Bash tool:
git checkout develop git flow release start $1 git add README.md CHANGELOG.md RELEASE_NOTES.md git commit -m "Prepare release $1: Strategic research complete" git flow release finish -m "Release $1" $1
Tag is created automatically by git flow finish. Verify tag exists: git tag -l "$1".
git push origin master --tags git push origin develop
Generate professional landing page for research results:
# Generate JSON + static HTML ./scripts/publish/generate-pages-v2.sh git add docs/index.html docs/sprints-data.json docs/.nojekyll git commit -m "Add GitHub Pages landing page for $1" git push origin main
This creates a beautiful landing page at
https://<username>.github.io/<repo>/ with:
If gh CLI available:
gh release create $1 \ --title "Strategic Research: Version $1" \ --notes-file RELEASE_NOTES.md \ --target master
Display release summary with version, tag, and release notes location.
If version format invalid, provide examples. If project incomplete, list missing requirements. If git operations fail, provide diagnostic information.
User receives confirmation of release creation with version tag and instructions for accessing release artifacts.