Automated summary
This skill defines the Git workflow for the QCC Plus project with branching strategy, commit conventions, and release process.
Strengths
- Clear separation of development, test, and production branches
- Standardized commit format enabling automatic changelog generation
- Strict Git safety rules preventing common destructive actions
- Integration of testing and code review for quality assurance
Limitations
- Rigid branch structure (test/main/prod) lacks flexibility for complex workflows
- Requires adherence to Conventional Commits, adding overhead
- May be overkill for small or solo projects
Use this skill when you need a disciplined Git workflow with defined environments and versioned releases.
Avoid this skill for rapid prototyping or projects where version management is not required.
Security analysis
SafeThe skill describes standard Git workflows and explicitly prohibits destructive operations (force push, hard reset, amend without explicit request). No external commands, data exfiltration, or obfuscated payloads. It only uses git commands for branch management, merging, and committing within the project’s defined workflow.
No concerns found
How this analysis is madeExamples
I want to start a new feature. Please switch to the test branch and prepare the Git workflow according to the project conventions.Merge the current test branch into main and create a new tag for release v1.2.0 following the qcc-git workflow.I fixed a bug in the health check endpoint. Please commit with the correct Conventional Commit format and ensure we are on the test branch.name: qcc-git description: Use for Git workflow, branch strategy, and commit conventions in qcc_plus project
QCC Plus Git 工作流
分支策略（强制）
强制规则: 所有开发工作必须在 test 分支进行，编写代码前必须确认当前分支。
| 分支 | 用途 | 说明 |
|------|------|------|
| test | 日常开发 | ✅ 在这里开发，推送后自动部署到测试环境（端口 8001） |
| main | 正式发布 | 合并测试通过的代码，用于打 tag 发布版本 |
| prod | 生产部署 | 部署到生产服务器（端口 8000） |
编写代码前检查
# 确认在 test 分支
git branch --show-current
# 如不在 test 分支
git checkout test
工作流程
# 1. 开发
git checkout test
# 编写代码
git push origin test
# 2. 发布
git checkout main
git merge test
git tag vX.Y.Z
git push origin vX.Y.Z
# 3. 部署
git checkout prod
git merge main
git push origin prod
Commit 格式
使用 Conventional Commits 格式：type: description
| 类型 | 说明 | 版本影响 |
|------|------|----------|
| feat | 新功能 | minor 升级 |
| fix | Bug 修复 | patch 升级 |
| feat! / fix! | 重大变更 | major 升级 |
| docs | 文档更新 | 不触发 |
| refactor | 代码重构 | 不触发 |
| test | 测试相关 | 不触发 |
| chore | 构建/工具 | 不包含在 CHANGELOG |
示例
feat: 添加健康检查 API 端点
fix: 修复节点切换延迟问题
docs: 更新 CLAUDE.md 文档结构
feat!: 重构 API 接口，移除 v1 兼容性
提交规范
Git 安全协议
- 永不更新 git config
- 永不运行破坏性命令（如 push --force, hard reset）除非用户明确请求
- 永不跳过 hooks（--no-verify, --no-gpg-sign）除非用户明确请求
- 永不强制推送到 main/master
- 避免
git commit --amend，仅在用户明确请求或添加 pre-commit hook 的编辑时使用 - 修改前总是检查作者：
git log -1 --format='%an %ae' - 永不提交更改除非用户明确要求
提交消息格式
使用 HEREDOC 确保格式正确：
git commit -m "$(cat <<'EOF'
Commit message here.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
EOF
)"
质量保证
测试要求
- 核心业务逻辑必须有单元测试
- 使用真实数据测试，避免过度 mock
- 测试边界条件和错误场景
- 使用
go test -race检测竞态条件
代码审查
- 所有合并到 main 的代码必须经过审查
- 检查错误处理是否完善
- 检查是否有资源泄漏（goroutine、文件句柄）
- 检查并发安全性
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/qcc-plus-git-workflow-mm5t89en/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/qcc-plus-git-workflow-mm5t89en' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/qcc-plus-git-workflow-mm5t89en/download' --output '.skill-downloads/qcc-plus-git-workflow-mm5t89en/SKILL.md.part' && mv '.skill-downloads/qcc-plus-git-workflow-mm5t89en/SKILL.md.part' '.skill-downloads/qcc-plus-git-workflow-mm5t89en/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/qcc-plus-git-workflow-mm5t89en/SKILL.md' && test -s '.skill-downloads/qcc-plus-git-workflow-mm5t89en/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/qcc-git' && cp -R '.skill-downloads/qcc-plus-git-workflow-mm5t89en' '.claude/skills/qcc-git'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/qcc-plus-git-workflow-mm5t89en'openskills read 'qcc-plus-git-workflow-mm5t89en'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/qcc-plus-git-workflow-mm5t89en/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.