Search

PythonReactSEOPDF

tools git workflows AI Skills

Discover tools git workflows skills, compare source repositories and read the instructions for each workflow.

Categories: tools git workflows

Showing 1,945–1,968 of 5,983

tools git workflows Clear filters

Browse skills

GitHub

generating-patches

oaustegard

Generates git patch files from codebase modifications for local application. Use when user mentions patch, diff, export changes, bring changes back, apply locally, or after editing uploaded codebases.

GitHub

codebase-inspection-protocol

Kaakati

Mandatory inspection procedures for understanding Rails codebase structure before writing any code. Use this skill FIRST before any code generation task to discover existing patterns, conventions, dependencies,...

GitHub

codebase-inspection-protocol

Kaakati

Mandatory inspection procedures for understanding Rails codebase structure before writing any code. Use this skill FIRST before any code generation task to discover existing patterns, conventions, dependencies,...

GitHub

merge-pr

troydai

Merge a GitHub PR and clean up the worktree. Use when merging a PR from a feature branch worktree that meets merging criteria.

GitHub

gwt

troydai

Manage git worktrees using gwt for branch-based workflow. Use when switching branches, creating worktrees, listing worktrees, or cleaning up after merging PRs.

GitHub

github-integration

ShunsukeHayashi

GitHub API integration for issues, pull requests, workflows, and repository management. Use when working with GitHub issues, PRs, releases, or CI/CD workflows.

GitHub

git-operations

ShunsukeHayashi

Git version control operations including status, branches, commits, diffs, and worktree management. Use when working with git repositories, reviewing changes, or managing branches.

GitHub

collect-for-pr

itsgrimetime

Collect pending worktree commits into a PR for review. Use this skill when subdirectory worktrees have accumulated 4-7+ commits that should be batched together and submitted for review. Invoked with /collect-fo...

GitHub

doc-organizer

Tempuss

Apply Progressive Disclosure principles to organize large documentation projects. Restructure docs into hierarchical structure, reduce token usage by 95%+, and create README files for navigation.

GitHub

clean-commits

troykelly

Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point

GitHub

issue-driven-development

troykelly

Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification

GitHub

conflict-resolution

troykelly

Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity

GitHub

worker-handover

troykelly

Defines context handover format when workers hit turn limit. Posts structured handover to GitHub issue comments enabling replacement workers to continue seamlessly.

GitHub

issue-prerequisite

troykelly

Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning

GitHub

deferred-finding

troykelly

Use when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full context, linked to parent, following full issue-driven-development process

GitHub

session-start

troykelly

Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work

GitHub

branch-discipline

troykelly

Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base

GitHub

comprehensive-review

troykelly

Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete

GitHub

pre-work-research

troykelly

Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach

GitHub

worker-dispatch

troykelly

Use to spawn isolated worker processes for autonomous issue work. Creates git worktrees, constructs worker prompts, and handles worker lifecycle.

GitHub

issue-lifecycle

troykelly

Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end

GitHub

project-status-sync

troykelly

Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields

GitHub

pr-creation

troykelly

Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary

GitHub

no-deferred-work

troykelly

Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission

The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.

More filters

Popularity

Popular tags