القائمة
Use this skill when managing git branches, releases, or hotfixes according to the Gitflow workflow. It enforces naming conventions and synchronization policies.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill to build, run, deploy, evaluate, and troubleshoot Go agents with Google's Agent Development Kit (`google.golang.org/adk`), including `llmagent` config, toolsets/skills, callbacks/plugins, sessions/state/memory, workflows, MCP/A2A, and current runtime/deployment patterns.
Use this skill to manage work in Beads (`bd`) 1.0+, a Dolt-backed issue tracker for AI agents, including issue lifecycle, agent setup, recovery, workflows, and multi-repo coordination.
Use this skill to initialize, configure, and run omnidist release workflows for Go projects (`init`, `ci`, `build`, `stage`, `verify`, `publish`) including npm and uv publishing setup.
Maintain Go repositories with high-quality standards, adhering to CI/CD, linting, and agent-friendly best practices.
Use this skill to install and use the upstream powerman/golangci-lint-strict config for an exact golangci-lint version by fetching the versioned config file unchanged.
Use this skill to build, refactor, or review Go applications using the Uber Fx dependency injection framework. It ensures idiomatic use of Fx for lifecycle management, module-based architecture, and boilerplate reduction.
| name | gitflow |
| description | Use this skill when managing git branches, releases, or hotfixes according to the Gitflow workflow. It enforces naming conventions and synchronization policies. |
| metadata | {"short-description":"Expert guidance on Gitflow branching and release management."} |
You are an expert in the Gitflow branching model. Your goal is to guide the user through the lifecycle of features, releases, and hotfixes while maintaining strict repository hygiene.
feature/*, bugfix/*, release/*, and hotfix/* naming conventions defined in the references.master AND develop).The project uses a standard Gitflow model.
Before creating any branch, run:
git checkout <source_branch>
git pull origin <source_branch>
git checkout -b <new_branch_name>
feature/ (from develop)bugfix/ (from develop)release/ (from develop)hotfix/ (from master)
Ref: references/branching-model.md