git-workflows
0
tdd-commit
変更をGitコミットしてTDDサイクルを完了する。REVIEWの次フェーズ。「コミットして」「commit」で起動。
morodomi
devops
结果数
10,480
符合搜索条件的技能
当前页
487
共 524 页
关键词
git
按名称、标签或描述搜索
git-workflows
0
gh-discussions-answerer
Find and answer unanswered GitHub discussions. Activate when user wants to contribute to open source discussions, help answer GitHub questions, or find discussions to answer. Delegates all work to subagents.
anntnzrb
devops
git-workflows
0
git-branch-namer
Use only when the user explicitly asks for a git branch name. Output one strong recommendation in a consistent pattern, with minimal, high-signal rationale.
iplaylf2
devops
automation-tools
0
project-documentation
Document a software project in this repo’s portfolio data model by extracting tech stack, learnings, screenshot, and live links from a Git repository and updating src/data/projects.ts for the ProjectPage.
paulb896
tools
git-workflows
0
gitworkflow
Gitを使用した開発ワークフローのルールです。ブランチの変更、Worktreeの作成、Pull Requestの作成時に必ず確認し遵守してください。
udondon1478
devops
automation-tools
0
git-master
Git operations mastery. Atomic commits, rebase/squash, history search (blame, bisect, log -S). Triggers on 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
opzero1
tools
automation-tools
0
feature-in-worktree
Develop features in isolated git worktrees with autonomous testing and iteration. Use when the user asks to develop a feature in a separate worktree, wants isolated feature development, or mentions working without affecting the current directory.
lgirndt
tools
git-workflows
0
agentuity-cli-git-link
Link a project to a GitHub repository. Requires authentication
agentuity
devops
git-workflows
0
git-pre-release-conflict
Use when asked to publish or sync a feature branch to pre in this repo, or to resolve complex git conflicts that occur in that release flow.
theoneLee
devops
git-workflows
0
merge-resolution
Merge conflict resolution conventions. Use when resolving git merge conflicts, especially in dependency files and lock files.
VectorInstitute
devops
git-workflows
0
create-pull-request
Create GitHub pull request with atomic Beads issue closure. MUST BE USED for opening PRs. Asks if work is complete - if YES, closes Beads issue BEFORE creating PR (JSONL merges atomically with code). If NO, creates draft PR with issue still open. Automatically links Beads tracking and includes Feature-Key. Use when user wants to open a PR, submit work for review, merge into master, or prepare for deployment, or when user mentions "ready for review", "create PR", "open PR", "merge conflicts", "CI checks needed", "branch ahead of master", PR creation, opening pull requests, deployment preparation, or submitting for team review.
stars-end
devops
git-workflows
0
pr-creator
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Use this when the user says "create pr", "make a pr", "open pull request", "submit pr", or "pr for these changes". Does NOT merge - stops when CI passes and provides the PR link.
neonwatty
devops
git-workflows
0
code-review-must-match-directory-name
Review a Gitlab Merge Request. Use when the user says "review" or "code review" or asks to review pull requests, merge requests, or analyze branch changes before merging
jwbaldwin
devops
automation-tools
0
repo-explore
Clone and explore external GitHub repositories to understand how libraries, frameworks, or dependencies work. Use when user provides a GitHub URL (github.com/owner/repo), asks "how does X library work", wants to look at source code for a dependency, asks about implementation details of an external package, or says "explore", "look at", or "check out" a repository. Automatically checks out the matching version tag when the repo is a dependency in the current project.
NavarrePratt
tools
automation-tools
0
commit-prepare
Prepare git commit messages following conventional commits. Activates on: commit, prepare commit, commit this, commit message, ready to commit, stage and commit
ByronWilliamsCPA
tools
automation-tools
0
semantic-commit-autostage
Autostage (git add) and commit changes using Semantic Commit format for fully automated workflows where Codex owns the full change set and the user should not manually stage files.
graysurf
tools
git-workflows
0
git-branching-strategy
This skill should be used when starting new feature work, mid-feature when wanting to add unrelated changes, when a branch has grown beyond 20 commits, or when unsure whether to create a new branch. Covers one-feature-one-branch rule, branch size targets, and when to split branches.
ImproperSubset
devops