fetching-github-user-data
Fetch comprehensive GitHub user data including profile, repositories, contributions, pull requests, issues, and statistics. Use when the user asks to fetch, download, or analyze GitHub user data.
Fetch comprehensive GitHub user data including profile, repositories, contributions, pull requests, issues, and statistics. Use when the user asks to fetch, download, or analyze GitHub user data.
React Native (Expo) 项目的 Git 和 GitHub 操作,包括分支管理、提交、推送、创建仓库、Pull Request、合并流程。当用户提到"git"、"github"、"提交"、"推送"、"分支"、"PR"、"合并"、"仓库"、"rebase"时使用此 skill。
Publish a plan as a GitHub Issue and create a branch to start implementation
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
Create a new feature branch, implement feature work, commit with semantic-commit, and open a PR with gh using standardized templates. Use when the user asks to develop a new feature, start a feature branch, or open a feature PR; also when asked to draft a feature PR based on the latest commit message.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Prepare complete PR content ready for creation via reedom-gh:pr-maker agent.
Generate commit messages following conventional commits with scope detection
TODO - describe when to trigger this skill (e.g., code review, PR review).
Create a new feature branch from a beads issue with proper prefix, worktree, and beads initialization
Create or update GitHub Pull Requests with the gh CLI, including deciding whether to create a new PR or only push based on existing PR merge status. Use when the user asks to open/create/edit a PR, generate a PR body/template, or says 'PRを出して/PR作成/gh pr'. Defaults: base=develop, head=current branch (same-branch only; never create/switch branches).
Generate clear Conventional Commit messages from git diffs; use when writing commits, reviewing staged work, or when the user requests a commit.
按照 Conventional Commits 规范执行高质量的 git 提交,处理暂存、消息生成及钩子修复。
Start new work on an issue with discovery, worktree/branch setup, TDD workflow, and draft PR creation. Use when beginning work on a GitHub issue.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Resolve a PR review comment thread using the GitHub CLI. ONLY use this as part of the pr-review-comments skill workflow after addressing a comment. Takes a comment ID (PRRC_...) and resolves its parent thread.
Iterate on a PR until CI passes and feedback is addressed. Use when fixing CI failures, addressing review comments, or continuously improving a PR until all checks are green. Automates the feedback-fix-push cycle.
Use when asked to recreate commits with narrative-quality history on the current branch.
Defines branch naming conventions for issue work. Use when creating branches for issues, understanding work status from branches, or linking commits to issues.
Git domain expert. Knows about: - Status, Switch, Create Branch, Commit, Pull, Push, Log Use when: - User asks about git operations - Context needed before starting work - Reviewing git status - Managing git workflow
Initialize memory bank structure for a new project workspace
Generates clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or asking about git commits.