GitHub
pr-template
Provides a structured template for Pull Request descriptions. Use when creating PRs, triggered by requests like "create a PR", "make a pull request", or "open a PR".
☆ 2View skill
blockchain git workflows AI Skills
Discover blockchain git workflows skills, compare source repositories and read the instructions for each workflow.
Categories: blockchain git workflows
blockchain git workflows Clear filters
Browse skills
GitHub
session-start
Bootstrap development sessions with automated startup rituals - checks recommendations, git status, launches scout + planner agents in parallel.
☆ 2View skill
GitHub
conventional-commits
Enforces conventional commit message and branch naming conventions with specific prefixes (feat, fix, docs, style, refactor, perf, test, chore). Use when creating git commits, suggesting branch names, reviewing...
☆ 2View skill
GitHub
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
☆ 2View skill
GitHub
git-pushing
Stage, commit, and push git changes with conventional commit messages with intelligent security checks. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their...
☆ 2View skill
GitHub
using-git-worktrees
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
☆ 2View skill
GitHub
finishing-a-development-branch
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
☆ 2View skill
GitHub
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
☆ 2View skill
GitHub
release
Automates the complete release process for this Obsidian plugin. This skill should be used when the user requests to publish a new version, bump version numbers, sync versions across files, update changelog, bu...
☆ 2View skill
GitHub
git-commit-message
Generate Conventional Commits git commit messages from the staged diff. Use this when the user asks to craft a commit message or when preparing a commit.
☆ 2View skill
GitHub
retrieve-diff-from-github-pr
Retrieve code diff from a GitHub Pull Request via GitHub API. Use this as the first step in a code review pipeline when reviewing GitHub PRs.
☆ 2View skill
GitHub
codereview-architect
Deep codebase context analysis like Greptile. Analyzes blast radius of changes, dependency graphs, and architectural consistency. Use when reviewing changes to core utilities, shared libraries, or database mode...
☆ 2View skill
GitHub
codereview-orchestrator
Triage and orchestrate code reviews. Analyzes PR intent, identifies touched surfaces, assesses risk, and routes to specialist skills. Does NOT perform detailed review - delegates to specialists. Supports full p...
☆ 2View skill
GitHub
retrieve-diff-from-commit
Retrieve code diff from a local git commit. Use this as the first step in a code review pipeline when reviewing local commits.
☆ 2View skill
GitHub
submit-github-review
Submit a code review to GitHub via the GitHub API. Use this as the final step in a code review pipeline to post review findings to a PR.
☆ 2View skill
GitHub
jj-changelog
Proactively use to generate or update a CHANGELOG.md file from Jujutsu commit history. Use when you need to create release notes, document changes between tags, or update the project changelog. Emphasizes break...
☆ 2View skill
GitHub
claude-compass-best-practices
Enforce Claude Compass development standards and best practices. This skill should be used when writing or modifying code in the Claude Compass repository, including parsers, database migrations, graph builders...
☆ 2View skill
GitHub
development-workflow-standards
Development process rules for this project including testing, branching, and commit standards. Use when implementing features, fixing bugs, or making any code changes.
☆ 2View skill
GitHub
fixing-github-issue
Fetches a GitHub issue, implements the fix, and verifies it. Use when: user wants to fix an issue, implement issue changes, or resolve a bug.
☆ 2View skill
GitHub
committing-changes
Creates logical, well-structured git commits following Conventional Commits. Use when: user mentions commit, committing, saving changes, or asks to organize changes into commits.
☆ 2View skill
GitHub
fixup-committing
Creates a fixup commit and performs autosquash rebase. Use when: user wants to fixup a commit, amend a previous commit, or squash into existing commit.
☆ 2View skill
GitHub
merging-branch
Merges a branch into current branch with conflict resolution. Use when: user wants to merge, combine branches, or integrate changes.
☆ 2View skill
GitHub
stashing-and-rebasing
Stashes changes, rebases onto main, and reapplies stash. Use when: user wants to update branch while preserving uncommitted work.
☆ 2View skill
GitHub
creating-sub-issue
Creates a sub-issue linked to a parent GitHub issue. Use when: user wants to create a sub-issue, break down an issue, or add child task.
☆ 2View skill
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.