Loading...
Loading...
Found 683 Skills
Work with Graphite (gt) for stacked PRs - creating, navigating, and managing PR stacks.
Manage Git commits using conventional commit format with atomic staging. Always generate plain git commands before running them and offer to let the user run them manually.
Sync all updated skills in ~/.claude/skills/ljg-* to the GitHub repo (ljg-skills). First push to the master branch (in org-mode output style), then switch to the md branch, perform basic markdown conversion, and push. Use when the user says '/ljg-push', 'push skills', 'sync skills', 'sync ljg', or whenever ljg-* skills are updated and need to be shipped. DO NOT use this for pushing non-ljg skills or arbitrary Git repos.
Commit changes and create a GitHub Pull Request. Used for requests such as "Commit and create a PR", "Commit my current work and create a pull request", "Push changes and create a PR". Handles a series of workflows including staging, commit message generation, branch creation, pushing, and PR creation. The PR body is written in Japanese.
Produces a gh CLI command to create a draft PR using the repo's PR template, filling the body from the current branch's commits and conversation context. Use when the user asks for a draft PR, create draft PR, open a PR with gh, or wants a PR command following the template.
Execute use when generating conventional commit messages from staged git changes. Trigger with phrases like "create commit message", "generate smart commit", "/commit-smart", or "/gc". Automatically analyzes changes to determine commit type (feat, fix, docs), identifies breaking changes, and formats according to conventional commit standards.
Stage changes, draft conventional commit messages, and commit with user confirmation. Use when user types /commit, asks to commit changes, or mentions creating a git commit.
lazygit terminal UI for git. Use for git operations.
Manage git worktrees for efficient multi-branch development. Use when you need to create worktrees for feature branches, organize worktree directories, clean up unused worktrees, or implement worktree-based workflows.
Update the title and body of one or more pull requests.
Resolve PR review comments
Merges valuable content into permanent documentation, then deletes source files. Use when you have untracked *_REPORT.md or *_ANALYSIS.md files, git status shows markdown artifacts that shouldn't be committed, preparing PR and need to clean up working artifacts, preserving insights from code reviews. Do not use when files are already in docs/ or skills/ locations. DO NOT use when: files are intentionally temporary scratch notes. DO NOT use when: source files have no extractable value.