Improve Git Workflows and Release Versioning
Unstructured branches, oversized commits, and unclear releases make changes difficult to review, revert, and communicate. This skill provides practical Git workflows for disciplined changes, safe collaboration, and predictable versioned releases.
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "git-workflow-and-versioning" from https://skillstore.io/skills/addyosmani-git-workflow-and-versioning.md and its manifest at https://skillstore.io/api/skills/addyosmani-git-workflow-and-versioning/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Utilisation de « git-workflow-and-versioning ». A small validation feature needs implementation, tests, and documentation.
RĂ©sultat attendu:
Branch: feature/email-validation. Commits: add validation, add tests, update documentation. Each commit remains independently reviewable.
Utilisation de « git-workflow-and-versioning ». A release adds a backward-compatible capability and deprecates an old endpoint.
RĂ©sultat attendu:
All 69 static findings are false positives caused by Markdown syntax, illustrative Git commands, fixed example paths, defensive secret-name checks, or sensitive-file exclusion advice. The skill contains no runtime execution, prompt injection, credential exfiltration, or network behavior; the main residual concern is user error when following destructive Git examples.
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
https://skillstore.io/skills/addyosmani-git-workflow-and-versioning/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/addyosmani-git-workflow-and-versioning?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/addyosmani-git-workflow-and-versioning?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-git-workflow-and-versioning/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/addyosmani-git-workflow-and-versioning.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>addyosmani. (2026). git-workflow-and-versioning security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-git-workflow-and-versioning/audits/1@techreport{addyosmani-addyosmani-git-workflow-and-versioning-2026,
author = {addyosmani},
title = {git-workflow-and-versioning security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/addyosmani-git-workflow-and-versioning/audits/1},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "git-workflow-and-versioning security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "addyosmani"
date-released: "2026-09-19"
url: "https://skillstore.io/skills/addyosmani-git-workflow-and-versioning/audits/1"
identifiers:
- type: other
value: "skillstore:addyosmani-git-workflow-and-versioning:audit:1"
description: "Skillstore immutable audit report identifier"
Turn a feature request into a short-lived branch plan with logical increments, tests, and commit boundaries.
Organize independent worktrees, branch names, merge points, and cleanup steps for multiple contributors or AI agents.
Choose a semantic version bump, create a tag plan, and draft a changelog focused on user impact and migration needs.
I need to make this change: [describe change]. Propose a branch name, three logical implementation slices, and a commit message for each slice.
Review this list of uncommitted changes: [paste file and change summary]. Group them into clean atomic commits and explain the staging order.
We have these parallel tasks: [list tasks]. Design a worktree layout, branch names, integration order, and conflict-reduction checks.
Given these changes and consumer impacts: [describe changes], recommend a semantic version bump, tag message, changelog sections, and migration notes.
Auteur
addyosmaniLicence
MIT
RĂ©vision Skillstore
r1
Avis de version
Lâauteur nâa dĂ©clarĂ© aucune version.
RĂ©f
5d5054f8a23586f9b500fece1cb613a9dffc787b
RĂ©cence de maintenance
19/09/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers
đ SKILL.md
Clarify User Intent Before You Build
Underspecified requests cause teams to build the wrong outcome and discover misalignment late. This skill runs a focused, one-question interview that turns ambiguity into confirmed intent.
Examiner le code selon cinq axes de qualité
Les modifications de code peuvent dissimuler des problĂšmes de fiabilitĂ©, de sĂ©curitĂ©, dâarchitecture, de lisibilitĂ© et de performances. Cette compĂ©tence applique un processus dâexamen structurĂ© et produit des retours hiĂ©rarchisĂ©s et exploitables.
Plan Work Into Verifiable Tasks
Large or vague software work can hide dependencies, missing acceptance criteria, and verification gaps. This skill converts a specification into ordered task slices with checkpoints, scope guidance, and clear completion conditions.
Document Decisions and Architecture Clearly
Teams lose context when important technical decisions remain in chat, code comments, or individual memory. This skill turns architectural reasoning, API guidance, project instructions, and release changes into structured documentation.
Build Accessible, Production-Ready Frontends
Frontend work can become inconsistent, inaccessible, or difficult to maintain. This skill guides component architecture, responsive layouts, state handling, and polished user experiences.
Discover and Apply Agent Skills
Teams often lose time choosing the right workflow for a software task. This skill maps task context to focused agent skills and a practical development sequence.
Create verified Jira issues and branches
par alvolutionor
Creating a Jira issue and matching repository branches can leave assignment, status, or sprint incomplete. This skill previews the plan, performs only requested writes, and verifies the resulting issue and branches.
Préparer des dossiers de release
par yaojingang
Les équipes de release rassemblent souvent les étapes de déploiement progressif, les notes de migration, les déclencheurs de retour arriÚre et les messages aux parties prenantes à différents endroits. Cette skill transforme ces éléments en un dossier de release structuré unique avec une orientation go/no-go.
GĂ©rer les workflows Git avec des standards dâĂ©quipe
par Atman36
Les équipes ont besoin de pratiques cohérentes pour les commits, les branches et les revues afin de garder un historique lisible. Cette compétence fournit à Claude, Codex et Claude Code une checklist pratique de workflow Git.
Diagnostiquer les Ă©checs de build avec une analyse des causes racines
par CleanExpo
Les blocages de build se cachent souvent derriĂšre des logs peu clairs, une configuration dĂ©fectueuse ou des tests incomplets. Cette skill guide Claude, Codex et Claude Code tout au long du diagnostic, de la planification du correctif, de la validation et de lâescalade.
RĂ©diger des commits Git conventionnels
par 0xmsc
Les développeurs perdent souvent du temps à transformer les changements indexés en historique de commits clair. Cette compétence guide les Conventional Commits, les changements atomiques et les étapes de revue git sûres.
Maßtriser les workflows Git avancés
par AutumnsGrove
Un historique Git complexe peut ĂȘtre difficile Ă rĂ©parer sans perdre du travail. Cette compĂ©tence fournit des workflows guidĂ©s pour le rebase, les conflits, le bisect, la rĂ©cupĂ©ration et la gestion des branches.