Loading...
Loading...
Found 409 Skills
Commit standards for Engram contributors. Trigger: Any commit creation, review, or branch cleanup.
Compare files and directories between git worktrees or worktree and current branch
Sync with remote repository using pull --rebase. Use when you need to update your local branch with remote changes.
Execute work plans efficiently while maintaining quality and finishing features
Fundamental Perforce operations including sync, edit, add, delete, submit, revert, and file state management.
Follow up on an existing PR by rebasing on the base branch, addressing reviewer comments, fixing CI issues, and pushing updates. Use when the user provides a PR URL or number and wants to get it ready for merge.
Programmatic hunk selection for Jujutsu — split, commit, or squash specific hunks without interactive prompts. Use when making partial commits or selective squashes.
Manage git repositories using the worktree pattern. This allows multiple branches to be checked out simultaneously in sibling directories.
Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.
Branch completion workflow - guides merge/PR/cleanup decisions after implementation is verified complete.
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
Generate a git-log-review-friendly commit message from repository changes. Use when you need to inspect staged changes, the current working tree relative to `HEAD`, or a commit-to-working-tree range and draft only the commit message text in a conventional-commit-style format, without creating the commit. Trigger for requests such as the skill `git:message`, the skill `git:message` with `staged`, the skill `git:message` with `HEAD`, or the skill `git:message` with `<commit>`, especially when the user wants a squash-ready summary of the most important changes.