{
  "schemaVersion": "1.0",
  "item": {
    "slug": "release-manager",
    "name": "release-manager",
    "source": "tencent",
    "type": "skill",
    "category": "开发工具",
    "sourceUrl": "https://clawhub.ai/alirezarezvani/release-manager",
    "canonicalUrl": "https://clawhub.ai/alirezarezvani/release-manager",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/release-manager",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=release-manager",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "README.md",
      "SKILL.md",
      "assets/sample_commits.json",
      "assets/sample_git_log.txt",
      "assets/sample_git_log_full.txt",
      "assets/sample_release_plan.json"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "slug": "release-manager",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-05-12T14:20:09.851Z",
      "expiresAt": "2026-05-19T14:20:09.851Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=release-manager",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=release-manager",
        "contentDisposition": "attachment; filename=\"release-manager-2.1.1.zip\"",
        "redirectLocation": null,
        "bodySnippet": null,
        "slug": "release-manager"
      },
      "scope": "item",
      "summary": "Item download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this item.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/release-manager"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/release-manager",
    "agentPageUrl": "https://openagent3.xyz/skills/release-manager/agent",
    "manifestUrl": "https://openagent3.xyz/skills/release-manager/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/release-manager/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Release Manager",
        "body": "Tier: POWERFUL\nCategory: Engineering\nDomain: Software Release Management & DevOps"
      },
      {
        "title": "Overview",
        "body": "The Release Manager skill provides comprehensive tools and knowledge for managing software releases end-to-end. From parsing conventional commits to generating changelogs, determining version bumps, and orchestrating release processes, this skill ensures reliable, predictable, and well-documented software releases."
      },
      {
        "title": "Core Capabilities",
        "body": "Automated Changelog Generation from git history using conventional commits\nSemantic Version Bumping based on commit analysis and breaking changes\nRelease Readiness Assessment with comprehensive checklists and validation\nRelease Planning & Coordination with stakeholder communication templates\nRollback Planning with automated recovery procedures\nHotfix Management for emergency releases\nFeature Flag Integration for progressive rollouts"
      },
      {
        "title": "Scripts",
        "body": "changelog_generator.py - Parses git logs and generates structured changelogs\nversion_bumper.py - Determines correct version bumps from conventional commits\nrelease_planner.py - Assesses release readiness and generates coordination plans"
      },
      {
        "title": "Documentation",
        "body": "Comprehensive release management methodology\nConventional commits specification and examples\nRelease workflow comparisons (Git Flow, Trunk-based, GitHub Flow)\nHotfix procedures and emergency response protocols"
      },
      {
        "title": "Semantic Versioning (SemVer)",
        "body": "Semantic Versioning follows the MAJOR.MINOR.PATCH format where:\n\nMAJOR version when you make incompatible API changes\nMINOR version when you add functionality in a backwards compatible manner\nPATCH version when you make backwards compatible bug fixes\n\nPre-release Versions\n\nPre-release versions are denoted by appending a hyphen and identifiers:\n\n1.0.0-alpha.1 - Alpha releases for early testing\n1.0.0-beta.2 - Beta releases for wider testing\n1.0.0-rc.1 - Release candidates for final validation\n\nVersion Precedence\n\nVersion precedence is determined by comparing each identifier:\n\n1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-alpha.beta < 1.0.0-beta\n1.0.0-beta < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1\n1.0.0-rc.1 < 1.0.0"
      },
      {
        "title": "Conventional Commits",
        "body": "Conventional Commits provide a structured format for commit messages that enables automated tooling:\n\nFormat\n\n<type>[optional scope]: <description>\n\n[optional body]\n\n[optional footer(s)]\n\nTypes\n\nfeat: A new feature (correlates with MINOR version bump)\nfix: A bug fix (correlates with PATCH version bump)\ndocs: Documentation only changes\nstyle: Changes that do not affect the meaning of the code\nrefactor: A code change that neither fixes a bug nor adds a feature\nperf: A code change that improves performance\ntest: Adding missing tests or correcting existing tests\nchore: Changes to the build process or auxiliary tools\nci: Changes to CI configuration files and scripts\nbuild: Changes that affect the build system or external dependencies\nbreaking: Introduces a breaking change (correlates with MAJOR version bump)\n\nExamples\n\nfeat(user-auth): add OAuth2 integration\n\nfix(api): resolve race condition in user creation\n\ndocs(readme): update installation instructions\n\nfeat!: remove deprecated payment API\nBREAKING CHANGE: The legacy payment API has been removed"
      },
      {
        "title": "Automated Changelog Generation",
        "body": "Changelogs are automatically generated from conventional commits, organized by:\n\nStructure\n\n# Changelog\n\n## [Unreleased]\n### Added\n### Changed  \n### Deprecated\n### Removed\n### Fixed\n### Security\n\n## [1.2.0] - 2024-01-15\n### Added\n- OAuth2 authentication support (#123)\n- User preference dashboard (#145)\n\n### Fixed\n- Race condition in user creation (#134)\n- Memory leak in image processing (#156)\n\n### Breaking Changes\n- Removed legacy payment API\n\nGrouping Rules\n\nAdded for new features (feat)\nFixed for bug fixes (fix)\nChanged for changes in existing functionality\nDeprecated for soon-to-be removed features\nRemoved for now removed features\nSecurity for vulnerability fixes\n\nMetadata Extraction\n\nLink to pull requests and issues: (#123)\nBreaking changes highlighted prominently\nScope-based grouping: auth:, api:, ui:\nCo-authored-by for contributor recognition"
      },
      {
        "title": "Version Bump Strategies",
        "body": "Version bumps are determined by analyzing commits since the last release:\n\nAutomatic Detection Rules\n\nMAJOR: Any commit with BREAKING CHANGE or ! after type\nMINOR: Any feat type commits without breaking changes\nPATCH: fix, perf, security type commits\nNO BUMP: docs, style, test, chore, ci, build only\n\nPre-release Handling\n\n# Alpha: 1.0.0-alpha.1 → 1.0.0-alpha.2\n# Beta: 1.0.0-alpha.5 → 1.0.0-beta.1  \n# RC: 1.0.0-beta.3 → 1.0.0-rc.1\n# Release: 1.0.0-rc.2 → 1.0.0\n\nMulti-package Considerations\n\nFor monorepos with multiple packages:\n\nAnalyze commits affecting each package independently\nSupport scoped version bumps: @scope/package@1.2.3\nGenerate coordinated release plans across packages"
      },
      {
        "title": "Release Branch Workflows",
        "body": "Git Flow\n\nmain (production) ← release/1.2.0 ← develop ← feature/login\n                                           ← hotfix/critical-fix\n\nAdvantages:\n\nClear separation of concerns\nStable main branch\nParallel feature development\nStructured release process\n\nProcess:\n\nCreate release branch from develop: git checkout -b release/1.2.0 develop\nFinalize release (version bump, changelog)\nMerge to main and develop\nTag release: git tag v1.2.0\nDeploy from main\n\nTrunk-based Development\n\nmain ← feature/login (short-lived)\n    ← feature/payment (short-lived)  \n    ← hotfix/critical-fix\n\nAdvantages:\n\nSimplified workflow\nFaster integration\nReduced merge conflicts\nContinuous integration friendly\n\nProcess:\n\nShort-lived feature branches (1-3 days)\nFrequent commits to main\nFeature flags for incomplete features\nAutomated testing gates\nDeploy from main with feature toggles\n\nGitHub Flow\n\nmain ← feature/login\n    ← hotfix/critical-fix\n\nAdvantages:\n\nSimple and lightweight\nFast deployment cycle\nGood for web applications\nMinimal overhead\n\nProcess:\n\nCreate feature branch from main\nRegular commits and pushes\nOpen pull request when ready\nDeploy from feature branch for testing\nMerge to main and deploy"
      },
      {
        "title": "Feature Flag Integration",
        "body": "Feature flags enable safe, progressive rollouts:\n\nTypes of Feature Flags\n\nRelease flags: Control feature visibility in production\nExperiment flags: A/B testing and gradual rollouts\nOperational flags: Circuit breakers and performance toggles\nPermission flags: Role-based feature access\n\nImplementation Strategy\n\n# Progressive rollout example\nif feature_flag(\"new_payment_flow\", user_id):\n    return new_payment_processor.process(payment)\nelse:\n    return legacy_payment_processor.process(payment)\n\nRelease Coordination\n\nDeploy code with feature behind flag (disabled)\nGradually enable for percentage of users\nMonitor metrics and error rates\nFull rollout or quick rollback based on data\nRemove flag in subsequent release"
      },
      {
        "title": "Release Readiness Checklists",
        "body": "Pre-Release Validation\n\nAll planned features implemented and tested\n Breaking changes documented with migration guide\n API documentation updated\n Database migrations tested\n Security review completed for sensitive changes\n Performance testing passed thresholds\n Internationalization strings updated\n Third-party integrations validated\n\nQuality Gates\n\nUnit test coverage ≥ 85%\n Integration tests passing\n End-to-end tests passing\n Static analysis clean\n Security scan passed\n Dependency audit clean\n Load testing completed\n\nDocumentation Requirements\n\nCHANGELOG.md updated\n README.md reflects new features\n API documentation generated\n Migration guide written for breaking changes\n Deployment notes prepared\n Rollback procedure documented\n\nStakeholder Approvals\n\nProduct Manager sign-off\n Engineering Lead approval\n QA validation complete\n Security team clearance\n Legal review (if applicable)\n Compliance check (if regulated)"
      },
      {
        "title": "Deployment Coordination",
        "body": "Communication Plan\n\nInternal Stakeholders:\n\nEngineering team: Technical changes and rollback procedures\nProduct team: Feature descriptions and user impact\nSupport team: Known issues and troubleshooting guides\nSales team: Customer-facing changes and talking points\n\nExternal Communication:\n\nRelease notes for users\nAPI changelog for developers\nMigration guide for breaking changes\nDowntime notifications if applicable\n\nDeployment Sequence\n\nPre-deployment (T-24h): Final validation, freeze code\nDatabase migrations (T-2h): Run and validate schema changes\nBlue-green deployment (T-0): Switch traffic gradually\nPost-deployment (T+1h): Monitor metrics and logs\nRollback window (T+4h): Decision point for rollback\n\nMonitoring & Validation\n\nApplication health checks\nError rate monitoring\nPerformance metrics tracking\nUser experience monitoring\nBusiness metrics validation\nThird-party service integration health"
      },
      {
        "title": "Hotfix Procedures",
        "body": "Hotfixes address critical production issues requiring immediate deployment:\n\nSeverity Classification\n\nP0 - Critical: Complete system outage, data loss, security breach\n\nSLA: Fix within 2 hours\nProcess: Emergency deployment, all hands on deck\nApproval: Engineering Lead + On-call Manager\n\nP1 - High: Major feature broken, significant user impact\n\nSLA: Fix within 24 hours\nProcess: Expedited review and deployment\nApproval: Engineering Lead + Product Manager\n\nP2 - Medium: Minor feature issues, limited user impact\n\nSLA: Fix in next release cycle\nProcess: Normal review process\nApproval: Standard PR review\n\nEmergency Response Process\n\nIncident declaration: Page on-call team\nAssessment: Determine severity and impact\nHotfix branch: Create from last stable release\nMinimal fix: Address root cause only\nExpedited testing: Automated tests + manual validation\nEmergency deployment: Deploy to production\nPost-incident: Root cause analysis and prevention"
      },
      {
        "title": "Rollback Planning",
        "body": "Every release must have a tested rollback plan:\n\nRollback Triggers\n\nError rate spike: >2x baseline within 30 minutes\nPerformance degradation: >50% latency increase\nFeature failures: Core functionality broken\nSecurity incident: Vulnerability exploited\nData corruption: Database integrity compromised\n\nRollback Types\n\nCode Rollback:\n\nRevert to previous Docker image\nDatabase-compatible code changes only\nFeature flag disable preferred over code rollback\n\nDatabase Rollback:\n\nOnly for non-destructive migrations\nData backup required before migration\nForward-only migrations preferred (add columns, not drop)\n\nInfrastructure Rollback:\n\nBlue-green deployment switch\nLoad balancer configuration revert\nDNS changes (longer propagation time)\n\nAutomated Rollback\n\n# Example rollback automation\ndef monitor_deployment():\n    if error_rate() > THRESHOLD:\n        alert_oncall(\"Error rate spike detected\")\n        if auto_rollback_enabled():\n            execute_rollback()"
      },
      {
        "title": "Release Metrics & Analytics",
        "body": "Key Performance Indicators\n\nLead Time: From commit to production\nDeployment Frequency: Releases per week/month\nMean Time to Recovery: From incident to resolution\nChange Failure Rate: Percentage of releases causing incidents\n\nQuality Metrics\n\nRollback Rate: Percentage of releases rolled back\nHotfix Rate: Hotfixes per regular release\nBug Escape Rate: Production bugs per release\nTime to Detection: How quickly issues are identified\n\nProcess Metrics\n\nReview Time: Time spent in code review\nTesting Time: Automated + manual testing duration\nApproval Cycle: Time from PR to merge\nRelease Preparation: Time spent on release activities"
      },
      {
        "title": "Tool Integration",
        "body": "Version Control Systems\n\nGit: Primary VCS with conventional commit parsing\nGitHub/GitLab: Pull request automation and CI/CD\nBitbucket: Pipeline integration and deployment gates\n\nCI/CD Platforms\n\nJenkins: Pipeline orchestration and deployment automation\nGitHub Actions: Workflow automation and release publishing\nGitLab CI: Integrated pipelines with environment management\nCircleCI: Container-based builds and deployments\n\nMonitoring & Alerting\n\nDataDog: Application performance monitoring\nNew Relic: Error tracking and performance insights\nSentry: Error aggregation and release tracking\nPagerDuty: Incident response and escalation\n\nCommunication Platforms\n\nSlack: Release notifications and coordination\nMicrosoft Teams: Stakeholder communication\nEmail: External customer notifications\nStatus Pages: Public incident communication"
      },
      {
        "title": "Release Planning",
        "body": "Regular cadence: Establish predictable release schedule\nFeature freeze: Lock changes 48h before release\nRisk assessment: Evaluate changes for potential impact\nStakeholder alignment: Ensure all teams are prepared"
      },
      {
        "title": "Quality Assurance",
        "body": "Automated testing: Comprehensive test coverage\nStaging environment: Production-like testing environment\nCanary releases: Gradual rollout to subset of users\nMonitoring: Proactive issue detection"
      },
      {
        "title": "Communication",
        "body": "Clear timelines: Communicate schedules early\nRegular updates: Status reports during release process\nIssue transparency: Honest communication about problems\nPost-mortems: Learn from incidents and improve"
      },
      {
        "title": "Automation",
        "body": "Reduce manual steps: Automate repetitive tasks\nConsistent process: Same steps every time\nAudit trails: Log all release activities\nSelf-service: Enable teams to deploy safely"
      },
      {
        "title": "Process Anti-patterns",
        "body": "Manual deployments: Error-prone and inconsistent\nLast-minute changes: Risk introduction without proper testing\nSkipping testing: Deploying without validation\nPoor communication: Stakeholders unaware of changes"
      },
      {
        "title": "Technical Anti-patterns",
        "body": "Monolithic releases: Large, infrequent releases with high risk\nCoupled deployments: Services that must be deployed together\nNo rollback plan: Unable to quickly recover from issues\nEnvironment drift: Production differs from staging"
      },
      {
        "title": "Cultural Anti-patterns",
        "body": "Blame culture: Fear of making changes or reporting issues\nHero culture: Relying on individuals instead of process\nPerfectionism: Delaying releases for minor improvements\nRisk aversion: Avoiding necessary changes due to fear"
      },
      {
        "title": "Getting Started",
        "body": "Assessment: Evaluate current release process and pain points\nTool setup: Configure scripts for your repository\nProcess definition: Choose appropriate workflow for your team\nAutomation: Implement CI/CD pipelines and quality gates\nTraining: Educate team on new processes and tools\nMonitoring: Set up metrics and alerting for releases\nIteration: Continuously improve based on feedback and metrics\n\nThe Release Manager skill transforms chaotic deployments into predictable, reliable releases that build confidence across your entire organization."
      }
    ],
    "body": "Release Manager\n\nTier: POWERFUL\nCategory: Engineering\nDomain: Software Release Management & DevOps\n\nOverview\n\nThe Release Manager skill provides comprehensive tools and knowledge for managing software releases end-to-end. From parsing conventional commits to generating changelogs, determining version bumps, and orchestrating release processes, this skill ensures reliable, predictable, and well-documented software releases.\n\nCore Capabilities\nAutomated Changelog Generation from git history using conventional commits\nSemantic Version Bumping based on commit analysis and breaking changes\nRelease Readiness Assessment with comprehensive checklists and validation\nRelease Planning & Coordination with stakeholder communication templates\nRollback Planning with automated recovery procedures\nHotfix Management for emergency releases\nFeature Flag Integration for progressive rollouts\nKey Components\nScripts\nchangelog_generator.py - Parses git logs and generates structured changelogs\nversion_bumper.py - Determines correct version bumps from conventional commits\nrelease_planner.py - Assesses release readiness and generates coordination plans\nDocumentation\nComprehensive release management methodology\nConventional commits specification and examples\nRelease workflow comparisons (Git Flow, Trunk-based, GitHub Flow)\nHotfix procedures and emergency response protocols\nRelease Management Methodology\nSemantic Versioning (SemVer)\n\nSemantic Versioning follows the MAJOR.MINOR.PATCH format where:\n\nMAJOR version when you make incompatible API changes\nMINOR version when you add functionality in a backwards compatible manner\nPATCH version when you make backwards compatible bug fixes\nPre-release Versions\n\nPre-release versions are denoted by appending a hyphen and identifiers:\n\n1.0.0-alpha.1 - Alpha releases for early testing\n1.0.0-beta.2 - Beta releases for wider testing\n1.0.0-rc.1 - Release candidates for final validation\nVersion Precedence\n\nVersion precedence is determined by comparing each identifier:\n\n1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-alpha.beta < 1.0.0-beta\n1.0.0-beta < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1\n1.0.0-rc.1 < 1.0.0\nConventional Commits\n\nConventional Commits provide a structured format for commit messages that enables automated tooling:\n\nFormat\n<type>[optional scope]: <description>\n\n[optional body]\n\n[optional footer(s)]\n\nTypes\nfeat: A new feature (correlates with MINOR version bump)\nfix: A bug fix (correlates with PATCH version bump)\ndocs: Documentation only changes\nstyle: Changes that do not affect the meaning of the code\nrefactor: A code change that neither fixes a bug nor adds a feature\nperf: A code change that improves performance\ntest: Adding missing tests or correcting existing tests\nchore: Changes to the build process or auxiliary tools\nci: Changes to CI configuration files and scripts\nbuild: Changes that affect the build system or external dependencies\nbreaking: Introduces a breaking change (correlates with MAJOR version bump)\nExamples\nfeat(user-auth): add OAuth2 integration\n\nfix(api): resolve race condition in user creation\n\ndocs(readme): update installation instructions\n\nfeat!: remove deprecated payment API\nBREAKING CHANGE: The legacy payment API has been removed\n\nAutomated Changelog Generation\n\nChangelogs are automatically generated from conventional commits, organized by:\n\nStructure\n# Changelog\n\n## [Unreleased]\n### Added\n### Changed  \n### Deprecated\n### Removed\n### Fixed\n### Security\n\n## [1.2.0] - 2024-01-15\n### Added\n- OAuth2 authentication support (#123)\n- User preference dashboard (#145)\n\n### Fixed\n- Race condition in user creation (#134)\n- Memory leak in image processing (#156)\n\n### Breaking Changes\n- Removed legacy payment API\n\nGrouping Rules\nAdded for new features (feat)\nFixed for bug fixes (fix)\nChanged for changes in existing functionality\nDeprecated for soon-to-be removed features\nRemoved for now removed features\nSecurity for vulnerability fixes\nMetadata Extraction\nLink to pull requests and issues: (#123)\nBreaking changes highlighted prominently\nScope-based grouping: auth:, api:, ui:\nCo-authored-by for contributor recognition\nVersion Bump Strategies\n\nVersion bumps are determined by analyzing commits since the last release:\n\nAutomatic Detection Rules\nMAJOR: Any commit with BREAKING CHANGE or ! after type\nMINOR: Any feat type commits without breaking changes\nPATCH: fix, perf, security type commits\nNO BUMP: docs, style, test, chore, ci, build only\nPre-release Handling\n# Alpha: 1.0.0-alpha.1 → 1.0.0-alpha.2\n# Beta: 1.0.0-alpha.5 → 1.0.0-beta.1  \n# RC: 1.0.0-beta.3 → 1.0.0-rc.1\n# Release: 1.0.0-rc.2 → 1.0.0\n\nMulti-package Considerations\n\nFor monorepos with multiple packages:\n\nAnalyze commits affecting each package independently\nSupport scoped version bumps: @scope/package@1.2.3\nGenerate coordinated release plans across packages\nRelease Branch Workflows\nGit Flow\nmain (production) ← release/1.2.0 ← develop ← feature/login\n                                           ← hotfix/critical-fix\n\n\nAdvantages:\n\nClear separation of concerns\nStable main branch\nParallel feature development\nStructured release process\n\nProcess:\n\nCreate release branch from develop: git checkout -b release/1.2.0 develop\nFinalize release (version bump, changelog)\nMerge to main and develop\nTag release: git tag v1.2.0\nDeploy from main\nTrunk-based Development\nmain ← feature/login (short-lived)\n    ← feature/payment (short-lived)  \n    ← hotfix/critical-fix\n\n\nAdvantages:\n\nSimplified workflow\nFaster integration\nReduced merge conflicts\nContinuous integration friendly\n\nProcess:\n\nShort-lived feature branches (1-3 days)\nFrequent commits to main\nFeature flags for incomplete features\nAutomated testing gates\nDeploy from main with feature toggles\nGitHub Flow\nmain ← feature/login\n    ← hotfix/critical-fix\n\n\nAdvantages:\n\nSimple and lightweight\nFast deployment cycle\nGood for web applications\nMinimal overhead\n\nProcess:\n\nCreate feature branch from main\nRegular commits and pushes\nOpen pull request when ready\nDeploy from feature branch for testing\nMerge to main and deploy\nFeature Flag Integration\n\nFeature flags enable safe, progressive rollouts:\n\nTypes of Feature Flags\nRelease flags: Control feature visibility in production\nExperiment flags: A/B testing and gradual rollouts\nOperational flags: Circuit breakers and performance toggles\nPermission flags: Role-based feature access\nImplementation Strategy\n# Progressive rollout example\nif feature_flag(\"new_payment_flow\", user_id):\n    return new_payment_processor.process(payment)\nelse:\n    return legacy_payment_processor.process(payment)\n\nRelease Coordination\nDeploy code with feature behind flag (disabled)\nGradually enable for percentage of users\nMonitor metrics and error rates\nFull rollout or quick rollback based on data\nRemove flag in subsequent release\nRelease Readiness Checklists\nPre-Release Validation\n All planned features implemented and tested\n Breaking changes documented with migration guide\n API documentation updated\n Database migrations tested\n Security review completed for sensitive changes\n Performance testing passed thresholds\n Internationalization strings updated\n Third-party integrations validated\nQuality Gates\n Unit test coverage ≥ 85%\n Integration tests passing\n End-to-end tests passing\n Static analysis clean\n Security scan passed\n Dependency audit clean\n Load testing completed\nDocumentation Requirements\n CHANGELOG.md updated\n README.md reflects new features\n API documentation generated\n Migration guide written for breaking changes\n Deployment notes prepared\n Rollback procedure documented\nStakeholder Approvals\n Product Manager sign-off\n Engineering Lead approval\n QA validation complete\n Security team clearance\n Legal review (if applicable)\n Compliance check (if regulated)\nDeployment Coordination\nCommunication Plan\n\nInternal Stakeholders:\n\nEngineering team: Technical changes and rollback procedures\nProduct team: Feature descriptions and user impact\nSupport team: Known issues and troubleshooting guides\nSales team: Customer-facing changes and talking points\n\nExternal Communication:\n\nRelease notes for users\nAPI changelog for developers\nMigration guide for breaking changes\nDowntime notifications if applicable\nDeployment Sequence\nPre-deployment (T-24h): Final validation, freeze code\nDatabase migrations (T-2h): Run and validate schema changes\nBlue-green deployment (T-0): Switch traffic gradually\nPost-deployment (T+1h): Monitor metrics and logs\nRollback window (T+4h): Decision point for rollback\nMonitoring & Validation\nApplication health checks\nError rate monitoring\nPerformance metrics tracking\nUser experience monitoring\nBusiness metrics validation\nThird-party service integration health\nHotfix Procedures\n\nHotfixes address critical production issues requiring immediate deployment:\n\nSeverity Classification\n\nP0 - Critical: Complete system outage, data loss, security breach\n\nSLA: Fix within 2 hours\nProcess: Emergency deployment, all hands on deck\nApproval: Engineering Lead + On-call Manager\n\nP1 - High: Major feature broken, significant user impact\n\nSLA: Fix within 24 hours\nProcess: Expedited review and deployment\nApproval: Engineering Lead + Product Manager\n\nP2 - Medium: Minor feature issues, limited user impact\n\nSLA: Fix in next release cycle\nProcess: Normal review process\nApproval: Standard PR review\nEmergency Response Process\nIncident declaration: Page on-call team\nAssessment: Determine severity and impact\nHotfix branch: Create from last stable release\nMinimal fix: Address root cause only\nExpedited testing: Automated tests + manual validation\nEmergency deployment: Deploy to production\nPost-incident: Root cause analysis and prevention\nRollback Planning\n\nEvery release must have a tested rollback plan:\n\nRollback Triggers\nError rate spike: >2x baseline within 30 minutes\nPerformance degradation: >50% latency increase\nFeature failures: Core functionality broken\nSecurity incident: Vulnerability exploited\nData corruption: Database integrity compromised\nRollback Types\n\nCode Rollback:\n\nRevert to previous Docker image\nDatabase-compatible code changes only\nFeature flag disable preferred over code rollback\n\nDatabase Rollback:\n\nOnly for non-destructive migrations\nData backup required before migration\nForward-only migrations preferred (add columns, not drop)\n\nInfrastructure Rollback:\n\nBlue-green deployment switch\nLoad balancer configuration revert\nDNS changes (longer propagation time)\nAutomated Rollback\n# Example rollback automation\ndef monitor_deployment():\n    if error_rate() > THRESHOLD:\n        alert_oncall(\"Error rate spike detected\")\n        if auto_rollback_enabled():\n            execute_rollback()\n\nRelease Metrics & Analytics\nKey Performance Indicators\nLead Time: From commit to production\nDeployment Frequency: Releases per week/month\nMean Time to Recovery: From incident to resolution\nChange Failure Rate: Percentage of releases causing incidents\nQuality Metrics\nRollback Rate: Percentage of releases rolled back\nHotfix Rate: Hotfixes per regular release\nBug Escape Rate: Production bugs per release\nTime to Detection: How quickly issues are identified\nProcess Metrics\nReview Time: Time spent in code review\nTesting Time: Automated + manual testing duration\nApproval Cycle: Time from PR to merge\nRelease Preparation: Time spent on release activities\nTool Integration\nVersion Control Systems\nGit: Primary VCS with conventional commit parsing\nGitHub/GitLab: Pull request automation and CI/CD\nBitbucket: Pipeline integration and deployment gates\nCI/CD Platforms\nJenkins: Pipeline orchestration and deployment automation\nGitHub Actions: Workflow automation and release publishing\nGitLab CI: Integrated pipelines with environment management\nCircleCI: Container-based builds and deployments\nMonitoring & Alerting\nDataDog: Application performance monitoring\nNew Relic: Error tracking and performance insights\nSentry: Error aggregation and release tracking\nPagerDuty: Incident response and escalation\nCommunication Platforms\nSlack: Release notifications and coordination\nMicrosoft Teams: Stakeholder communication\nEmail: External customer notifications\nStatus Pages: Public incident communication\nBest Practices\nRelease Planning\nRegular cadence: Establish predictable release schedule\nFeature freeze: Lock changes 48h before release\nRisk assessment: Evaluate changes for potential impact\nStakeholder alignment: Ensure all teams are prepared\nQuality Assurance\nAutomated testing: Comprehensive test coverage\nStaging environment: Production-like testing environment\nCanary releases: Gradual rollout to subset of users\nMonitoring: Proactive issue detection\nCommunication\nClear timelines: Communicate schedules early\nRegular updates: Status reports during release process\nIssue transparency: Honest communication about problems\nPost-mortems: Learn from incidents and improve\nAutomation\nReduce manual steps: Automate repetitive tasks\nConsistent process: Same steps every time\nAudit trails: Log all release activities\nSelf-service: Enable teams to deploy safely\nCommon Anti-patterns\nProcess Anti-patterns\nManual deployments: Error-prone and inconsistent\nLast-minute changes: Risk introduction without proper testing\nSkipping testing: Deploying without validation\nPoor communication: Stakeholders unaware of changes\nTechnical Anti-patterns\nMonolithic releases: Large, infrequent releases with high risk\nCoupled deployments: Services that must be deployed together\nNo rollback plan: Unable to quickly recover from issues\nEnvironment drift: Production differs from staging\nCultural Anti-patterns\nBlame culture: Fear of making changes or reporting issues\nHero culture: Relying on individuals instead of process\nPerfectionism: Delaying releases for minor improvements\nRisk aversion: Avoiding necessary changes due to fear\nGetting Started\nAssessment: Evaluate current release process and pain points\nTool setup: Configure scripts for your repository\nProcess definition: Choose appropriate workflow for your team\nAutomation: Implement CI/CD pipelines and quality gates\nTraining: Educate team on new processes and tools\nMonitoring: Set up metrics and alerting for releases\nIteration: Continuously improve based on feedback and metrics\n\nThe Release Manager skill transforms chaotic deployments into predictable, reliable releases that build confidence across your entire organization."
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/alirezarezvani/release-manager",
    "publisherUrl": "https://clawhub.ai/alirezarezvani/release-manager",
    "owner": "alirezarezvani",
    "version": "2.1.1",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/release-manager",
    "downloadUrl": "https://openagent3.xyz/downloads/release-manager",
    "agentUrl": "https://openagent3.xyz/skills/release-manager/agent",
    "manifestUrl": "https://openagent3.xyz/skills/release-manager/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/release-manager/agent.md"
  }
}