Loading...
Loading...
Found 334 Skills
Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
Manage Git submodules for including external repositories within a main repository. Use when working with external libraries, shared modules, or managing dependencies as separate Git repositories.
Use when you need to resolve an in-progress git merge/rebase conflict.
Create and checkout a new git branch with smart validation and GitHub issue integration
Quick remote sync shortcut. Use when user says "/sync", "동기화", "pull", "git pull", or wants to pull latest changes from remote. Defaults to pulling from origin main.
Conventional Commits v1.0.0 branch naming and commit message standards for GitHub and GitLab projects. Use when creating branches, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases, parseable changelog generation, or automatic issue closing.
A comprehensive Git agent skill combining strategic workflows, strict conventional commit standards, and safe execution protocols. Acts as a senior engineer to guide users through atomic, verifiable, and standardized git operations.
Review AI-generated code changes before committing using GitHuman. Use when reviewing code changes, creating code reviews, checking what the AI agent wrote, preparing to commit, or when user mentions "review", "GitHuman", or "before commit".
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.
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.
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
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.