技能 git-workflow-and-versioning

📦

git-workflow-and-versioning

Name: git-workflow-and-versioning
Author: addyosmani

内容修订 r1 安全 ⚙️ 外部命令📁 文件系统访问🔑 环境变量

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.

支持: Claude Codex Code(CC)

🥉 77 青铜

使用我的智能体安装

将此请求复制给你的智能体，其中包含权威 Skill 页面和清单。

智能体请求

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.

你的智能体仍应展示其计划，并按安全策略请求必要确认。

Agent 可读资源

当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。

Markdown 详情 GET /skills/addyosmani-git-workflow-and-versioning.md 已签名 manifest GET /api/skills/addyosmani-git-workflow-and-versioning/manifest 已签名 lockfile GET /api/skills/addyosmani-git-workflow-and-versioning/lockfile

测试它

正在使用“git-workflow-and-versioning”。 A small validation feature needs implementation, tests, and documentation.

预期结果:

Branch: feature/email-validation. Commits: add validation, add tests, update documentation. Each commit remains independently reviewable.

正在使用“git-workflow-and-versioning”。 A release adds a backward-compatible capability and deprecates an old endpoint.

预期结果:

Recommended bump: minor version
Changelog sections: Added and Deprecated
Include the replacement endpoint and the planned removal version

安全审计

安全

v1 • 2026/9/19 打开版本化报告

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.

已扫描文件

356

分析行数

复核项

已忽略误报

风险因素

⚙️ 外部命令 (50)

SKILL.md:20 SKILL.md:22-26 SKILL.md:26-38 SKILL.md:38-44 SKILL.md:44-52 SKILL.md:52-63 SKILL.md:63-69 SKILL.md:69-79 SKILL.md:79-82 SKILL.md:82-86 SKILL.md:86-89 SKILL.md:89-90 SKILL.md:90-91 SKILL.md:91-92 SKILL.md:92-93 SKILL.md:93-94 SKILL.md:94-100 SKILL.md:100-107 SKILL.md:107-113 SKILL.md:113-115 SKILL.md:115-119 SKILL.md:119-125 SKILL.md:125-131 SKILL.md:131-133 SKILL.md:133-140 SKILL.md:140-145 SKILL.md:145-151 SKILL.md:151-165 SKILL.md:165-175 SKILL.md:175-187 SKILL.md:187-189 SKILL.md:189-195 SKILL.md:195-207 SKILL.md:207-215 SKILL.md:215-230 SKILL.md:230-234 SKILL.md:234-242 SKILL.md:242-246 SKILL.md:246-247 SKILL.md:247 SKILL.md:248 SKILL.md:252-268 SKILL.md:268-276 SKILL.md:276-278 SKILL.md:278-282 SKILL.md:282-284 SKILL.md:284-290 SKILL.md:290-293 SKILL.md:293-299 SKILL.md:299

📁 文件系统访问 (4)

SKILL.md:153 SKILL.md:154 SKILL.md:158 SKILL.md:164

🔑 环境变量 (1)

SKILL.md:220

最新一次完成的静态与语义审计未检测到已确认的安全发现。这并不能证明该 Skill 没有副作用。

审计者: codex

分享与引用此报告

分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据，不判断该 Skill 是否安全。

打开版本化报告

复制报告链接

https://skillstore.io/skills/addyosmani-git-workflow-and-versioning/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 徽章

[![Skillstore security assessment](https://skillstore.io/badges/skills/addyosmani-git-workflow-and-versioning/security.svg)](https://skillstore.io/skills/addyosmani-git-workflow-and-versioning?utm_source=security_passport_badge)

HTML 徽章

<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>

学术引用 (APA · BibTeX · CFF)

APA 引用

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

BibTeX 引用

@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}
}

CITATION.cff

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"

Skillstore 评分

评分依据证据置信度: 中

架构

可维护性

内容

社区

规范符合性

你能构建什么

Plan a small feature

Turn a feature request into a short-lived branch plan with logical increments, tests, and commit boundaries.

Coordinate parallel agent work

Organize independent worktrees, branch names, merge points, and cleanup steps for multiple contributors or AI agents.

Prepare a versioned release

Choose a semantic version bump, create a tag plan, and draft a changelog focused on user impact and migration needs.

试试这些提示

Create a simple Git plan

I need to make this change: [describe change]. Propose a branch name, three logical implementation slices, and a commit message for each slice.

Split a messy worktree

Review this list of uncommitted changes: [paste file and change summary]. Group them into clean atomic commits and explain the staging order.

Coordinate parallel work

We have these parallel tasks: [list tasks]. Design a worktree layout, branch names, integration order, and conflict-reduction checks.

Plan a release

Given these changes and consumer impacts: [describe changes], recommend a semantic version bump, tag message, changelog sections, and migration notes.

最佳实践

Keep each commit focused on one logical change and explain why it exists.
Run tests, linting, type checks, and staged-diff reviews before committing.
Treat tags and changelogs as part of the release contract for consumers.

避免

Do not combine formatting, refactoring, and feature work in one commit.
Do not commit secrets, environment files, build output, or unrelated generated files.
Do not hide breaking behavior under a patch or minor version number.

常见问题

Does this skill execute Git commands?

No. It provides workflow guidance and command examples for a developer or agent to review and run.

Should every change use a feature branch?

Use the team default. The skill recommends short-lived branches and supports trunk-based workflows.

How small should commits be?

Each commit should represent one logical, reviewable change. The suggested target is about 100 lines when practical.

When should a version be major?

Use a major version when consumers must change code or behavior because of a breaking change.

What belongs in a changelog?

Record user-relevant additions, changes, fixes, deprecations, removals, security updates, and migration guidance.

Can this replace repository-specific policy?

No. Adapt the recommendations to repository rules, approval requirements, release automation, and deployment controls.

开发者详情

作者

addyosmani

许可证

MIT

Skillstore 修订

版本提示

作者未声明版本。

仓库

https://github.com/addyosmani/agent-skills/tree/c004a74784a08295d52749b04cda634125b9a581/skills/git-workflow-and-versioning

引用

5d5054f8a23586f9b500fece1cb613a9dffc787b

维护新鲜度

2026/9/19

使用量

0 次下载 · 0 次浏览

文件结构

📄 SKILL.md

addyosmani 的更多技能

查看全部

📦

code-review-and-quality

从五个质量维度审查代码

代码变更可能隐藏正确性、安全性、架构、可读性和性能问题。此技能采用结构化审查流程，并提供按优先级排列、可执行的反馈。

编码与开发查看

📦

interview-me

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.

沟通查看

📦

planning-and-task-breakdown

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.

效率查看

📦

documentation-and-adrs

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.

文档查看

📦

frontend-ui-engineering

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.

设计与创意查看

📦

security-and-hardening

Harden Applications Against Security Risks

Security reviews can miss trust boundaries and unsafe data flows. This skill supplies threat-modeling prompts, OWASP patterns, and practical review checklists.

安全与合规查看

查看全部

📦