project-init
Guidance for initializing new projects. Use framework/package manager commands instead of manual scaffolding.
Discover databases git workflows skills, compare source repositories and read the instructions for each workflow.
Guidance for initializing new projects. Use framework/package manager commands instead of manual scaffolding.
Generates .gitignore file for Git version control exclusions. Defines files and directories to exclude from version control like node_modules, build artifacts, and local environment files.
Generates .lintstagedrc configuration to automatically fix and format staged files before commit. Runs ESLint, Stylelint, and Prettier on staged files.
Generates Husky Git hooks configuration with pre-commit checks. Creates .husky/pre-commit file for running linting, testing, and formatting before commits.
Documentation drift detection and knowledge-base hygiene. Use to ensure docs match implementation.
Git workflow assistant for common tasks. Use this skill when the user asks to: - Create a commit with proper conventional commit formatting (feat, fix, docs, style, refactor, test, chore) - Create a new feature...
This skill should be used when the user asks to "create a commit", "write commit message", "create a pull request", "generate changelog", "manage branches", "git workflow", "merge strategy", "PR description", o...
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
Use when running /ltk:sync-submodules, updating submodules, or needing to "sync", "merge", "adapt", "learn from" other Claude Code plugins or repos
Use when creating "changelog", "release notes", "version updates", generating "CHANGELOG.md", or asking about "git history to changelog", "commit summary", "what changed since last release"
Use when requesting code review, receiving code review feedback, before merging, or when handling reviewer suggestions - covers both giving and receiving review
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
Sync modified and new files to chezmoi repository and push to GitHub. Use when Claude Code has modified or created files in a chezmoi-managed directory and needs to re-add them to chezmoi, commit changes, and p...
CI/CD pipeline best practices including GitHub Actions, testing, and deployment strategies.
Git best practices and workflows including conventional commits, branching strategies, and collaboration patterns.
Enforce pre-commit testing and validation before any git commit in the readathon project
Follow project-wide development conventions including consistent project structure, clear documentation, version control best practices, environment configuration, dependency management, code review processes,...
Provides Git workflow guidance for branching, committing, merging, and creating pull requests. Use when creating commits, making PRs, managing branches, resolving conflicts, or asking about Git workflow.
Help address GitHub PR review comments. Use when the user mentions PR reviews, code review feedback, reviewer comments, or needs to resolve review threads.
Code review workflow for evaluating changes against standards. Use when reviewing pull requests, commits, or diffs.
Automated git workflow helpers for common development tasks like creating feature branches, cleaning up merged branches, and interactive rebasing. Use when the user mentions git branching, branch cleanup, featu...
병렬 SPEC 개발을 위한 Git worktree 관리 시스템으로 고립된 워크스페이스, 자동 등록, 그리고 seamless Do 통합을 제공
Create and submit a GitHub pull request from a fork to the upstream source repo. Use when asked to open or submit a PR for the current branch or recent changes.
Commit staged or unstaged git changes with a clear, informative message (subject + body). Use when asked to commit work, finalize edits, or generate a commit message after changes are made.
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.