git-workflow
建立更好的拉取請求
也可从以下获取: 0xDarkMatter,0xDarkMatter,Joseph OBrien,Cain96,Barnhardt-Enterprises-Inc,AI-Vibe-Prompts,Doyajin174,supercent-io
團隊常因拉取請求不一致、缺乏上下文而影響審查效率。本技能提供結構化模板、分支命名規範與合併策略,協助你簡化 git 工作流程。
下载技能 ZIP
在 Claude 中上传
前往 设置 → 功能 → 技能 → 上传技能
开启并开始使用
测试它
正在使用“git-workflow”。 Help me create a pull request for a new feature that adds OAuth2 login.
预期结果:
- Title: feat(auth): add OAuth2 integration
- Summary: Adds Google and GitHub OAuth2 login options. Users can now sign in with their existing accounts. Session management updated for persistent login.
- Test Plan: Add unit tests for OAuth flow, integration tests with mock provider, manual testing with real OAuth accounts.
- Checklist: Code follows style guidelines, self-review completed, documentation updated, no new warnings.
正在使用“git-workflow”。 Create a bug fix PR for fixing a memory leak in the data processing module.
预期结果:
- Title: fix(memory): resolve leak in data processing module
- Summary: Identified and fixed memory leak caused by uncleared event listeners. Added proper cleanup in component unmount lifecycle.
- Root cause: Event listeners not removed on component unmount caused accumulated references.
- Test Plan: Stress test with 1000+ cycles, memory profiler shows stable usage, no regression in functionality.
正在使用“git-workflow”。 Help me write a refactor PR for extracting utility functions into a shared module.
预期结果:
- Title: refactor(utils): extract common functions to shared module
- Summary: Moved 15 duplicate utility functions to a new utils/shared.js module. Reduced code duplication across 8 files.
- Test Plan: All existing unit tests pass, integration tests confirm behavior unchanged, linting passes on affected files.
安全审计
安全Pure documentation skill containing only markdown files with git workflow templates and PR conventions. No executable code, scripts, network calls, or filesystem access. All 48 static findings are false positives caused by the scanner misinterpreting markdown syntax and JSON metadata as security patterns.
风险因素
⚙️ 外部命令 (27)
质量评分
你能构建什么
標準化團隊 PR
在開發團隊中建立一致的拉取請求模板與分支命名方式。
改善貢獻者 PR
引導貢獻者提交文件完備、測試計畫清楚的拉取請求。
定義合併策略
為不同分支類型選擇合適的合併策略並記錄規範。
试试这些提示
Help me create a pull request for a new feature called user authentication. Include a clear title, summary of changes, test plan, and checklist.
I fixed a bug where login failed on mobile devices. Create a bug fix PR template with root cause analysis and regression test plan.
I refactored the database utility module. Help me write a refactor PR that confirms no behavior changes and existing tests pass.
Our API signature changed from oldMethod() to newMethod(options). Create breaking changes documentation with migration guide.
最佳实践
- 在 PR 標題中使用慣例提交格式,以便自動產生變更記錄
- 提供具體測試計畫,包含逐步指示與預期結果
- 以清楚的前後對照範例與遷移步驟記錄重大變更
避免
- 提交標題含糊的 PR,例如「fix stuff」或「updates」
- 缺少測試計畫,或僅貼上不具體的通用清單
- 忘記連結相關議題或說明為何需要此變更
常见问题
這個技能相容哪些工具?
PR 複雜度是否有上限?
是否與 Git 託管平台整合?
我的程式碼或資料會被儲存嗎?
如果模板不符合我的專案怎麼辦?
這與 git commit hooks 有何不同?
开发者详情
许可证
UNLICENSED
引用
main
文件结构