{"enrichment":{"faq":[{"a":"semantic-versioning automates version bumping by analyzing your commit history and applying semantic versioning conventions. When you use conventional commits (feat:, fix:, BREAKING CHANGE:), the skill determines whether to increment the major, minor, or patch version number automatically. Tools like semantic-release and standard-version integrate with your CI/CD pipeline to calculate the next version, create git tags, and trigger releases without manual intervention.","q":"How does semantic-versioning automate version bumping?"},{"a":"semantic-versioning uses conventional commits to determine version increments by mapping commit types to semver changes. A 'fix:' commit triggers a patch bump, a 'feat:' commit triggers a minor bump, and a commit with 'BREAKING CHANGE:' in the footer triggers a major bump. This standardized commit format allows semantic-versioning to parse your git history automatically and calculate the correct version number without ambiguity or manual decision-making.","q":"What is the relationship between conventional commits and version increments in semantic-versioning?"},{"a":"Yes, semantic-versioning generates changelogs automatically from your commit history by extracting and organizing conventional commits. Tools configured through this skill parse commits since the last release, group them by type (features, fixes, breaking changes), and format them into a readable changelog. This changelog generation happens as part of the automated release process, ensuring your release notes always reflect the actual changes in each version.","q":"Can semantic-versioning generate changelogs automatically from commit history?"},{"a":"semantic-versioning enables CI/CD release pipeline setup by configuring tools like semantic-release or standard-version to run on your repository. You define rules for when releases should trigger (typically on commits to your main branch), and the skill handles version calculation, changelog generation, git tagging, and package publishing automatically. The pipeline integrates with your version control system to detect changes and orchestrate the entire release workflow without manual steps.","q":"How do you set up a CI/CD release pipeline using semantic-versioning?"},{"a":"semantic-versioning supports multi-package version management through tools like Lerna and Changesets. These tools allow you to manage interdependent packages within a monorepo, coordinating version bumps across packages and tracking which packages changed in each release. This is particularly useful for projects with multiple related packages that need to stay synchronized or have independent versioning strategies.","q":"Does semantic-versioning support managing versions across multiple packages?"},{"a":"semantic-versioning follows these semver rules: a major version bump (X.0.0) indicates breaking changes, a minor version bump (x.Y.0) indicates new backward-compatible features, and a patch version bump (x.y.Z) indicates backward-compatible bug fixes. The skill applies these rules automatically based on your conventional commits, so 'BREAKING CHANGE:' commits increment major, 'feat:' commits increment minor, and 'fix:' commits increment patch versions.","q":"What are the major, minor, and patch versioning rules in semantic-versioning?"}],"shadow_tags":["release-automation","version-control","commit-analysis","changelog-generation","ci-cd-integration","multi-package-management","prerelease-strategy","breaking-change-tracking"],"summary_rewrite":"This skill equips AI agents to handle version management workflows by applying semantic versioning conventions to your release pipeline. Streamline version bumping, changelog generation, and release tagging\u2014letting your automation handle the repetitive parts of version control so your team focuses on what matters."},"files":[{"bytes":10657,"path":"devops/release/semantic-versioning/SKILL.md","sha256":"50dd655ca9a3a488050ff26ebd5c4d73d26b1ac84614f523fe7a0b73219d9083","url":"https://skillfed.io/files/BagelHole/DevOps-Security-Agent-Skills/semantic-versioning/0bd4485f/SKILL.md"}],"id":"BagelHole/DevOps-Security-Agent-Skills/semantic-versioning","links":{"html":"https://skillfed.io/BagelHole/DevOps-Security-Agent-Skills/semantic-versioning","md":"https://skillfed.io/BagelHole/DevOps-Security-Agent-Skills/semantic-versioning.md","repo":"https://github.com/BagelHole/DevOps-Security-Agent-Skills"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":4,"language":"Shell","last_updated":"2026-05-22","license":"MIT","name":"semantic-versioning","publisher":"BagelHole","stars":44},"relations":{"similar":[{"id":"CuriousLearner/devkit/changelog-generator"},{"id":"patricio0312rev/skills/release-automation-builder"},{"id":"Pixel-Process-UG/superkit-agents/git-commit-helper"},{"id":"UfoMiao/zcf/zcf-release"},{"id":"itechmeat/llm-code/commits"},{"id":"NikiforovAll/claude-code-rules/version-bump"},{"id":"oakoss/agent-skills/changesets"},{"id":"bmad-labs/skills/release-please"},{"id":"aj-geddes/useful-ai-prompts/semantic-versioning"},{"id":"maximhq/bifrost/changelog-writer"}]},"slug":{"owner":"BagelHole","repo":"DevOps-Security-Agent-Skills","skill":"semantic-versioning"},"version":"0bd4485f"}