git-2025-features
Git 2.49+ features including reftables, sparse-checkout, partial clone, git-backfill, and worktrees
Découvrez les skills blockchain git workflows, comparez leurs dépôts et consultez leurs instructions.
Git 2.49+ features including reftables, sparse-checkout, partial clone, git-backfill, and worktrees
Complete Python GitHub Actions system. PROACTIVELY activate for: (1) uv-based CI workflows (10-100x faster), (2) Matrix testing across Python versions, (3) Dependency caching with setup-uv, (4) Parallel test ex...
Reimplement the current Git branch on a fresh branch off `main` with a clean, narrative-quality commit history.
Commit changes with an emphasis on tidiness and reviewability: small, focused commits, with clear rationale in messages.
Verify a PR is ready for merge (CI passing, approvals, no conflicts). Use before merging to ensure all requirements met.
Diagnose and fix CI/CD failures by analyzing logs, reproducing locally, and applying fixes. Use when CI checks fail on pull requests.
Retrieve all review comments from a pull request using the GitHub API. Use when you need to see what feedback has been provided on a PR.
Validate GitHub Actions workflow files for syntax, best practices, and correctness. Use before committing workflow changes or when workflows fail.
Create isolated git worktrees for parallel development. Use when working on multiple issues simultaneously.
Create GitHub Actions workflows for automated package building and distribution. Use in package phase to automate .mojopkg building and release creation.
Read context from GitHub issue including body and comments. Use before starting implementation work or when prior context is needed.
Remove merged or stale git worktrees. Use after PRs are merged, work is done, or when worktrees are no longer needed.
DEPRECATED: The notes/plan/ directory has been removed. Planning is now done directly through GitHub issues. See gh-read-issue-context and gh-post-issue-update skills instead.
Switch between git worktrees for parallel development. Use when working on multiple issues simultaneously.
Sync git worktrees with remote and main branch changes. Use to keep long-running feature branches up-to-date.
Create a pull request properly linked to a GitHub issue using gh pr create --issue. Use when creating a PR that implements or addresses a specific issue.
Create changelog from git commits. Use when preparing release notes.
Comprehensively review a pull request including code changes, CI status, and adherence to project standards. Use when asked to review a PR.
Post structured updates to GitHub issues. Use to report progress, findings, and implementation notes directly to issues.
DEPRECATED: The notes/plan/ directory has been removed. Planning is now done directly through GitHub issues. See gh-read-issue-context and gh-post-issue-update skills instead.
DEPRECATED: The notes/plan/ directory has been removed. Planning is now done directly through GitHub issues. See gh-read-issue-context and gh-post-issue-update skills instead.
Check CI/CD status of a pull request including workflow runs and test results. Use when verifying if PR checks are passing or investigating CI failures.
Address PR review feedback by making changes and replying to comments. Use when a PR has open review comments needing responses.
Reply to PR review comments using the correct GitHub API endpoint. Use when responding to inline code review feedback (not gh pr comment).
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.