Loading...
Loading...
Found 355 Skills
Manage git-tracked directories correctly - never create .gitkeep files in directories that will immediately contain tracked files
Design PM-friendly technical architecture for features. No code, only high-level design decisions.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Sync with remote repository using pull --rebase. Use when you need to update your local branch with remote changes.
Merge validated feature to main via PR, tag release, cleanup worktree. Use after /feature-validate passes. Use for "release feature", "merge feature", "ship it", or "/feature-release". Do NOT use without passing validation or for hotfixes that skip the pipeline.
Use when starting a new feature branch, creating isolated development environments, or working on multiple tasks simultaneously without stashing or switching branches. Triggers: user says "worktree", "new branch for work", "parallel development", "isolated environment", needs to work on two things at once.
Use when the user asks to commit changes, organize commits, write commit messages, or split working-tree changes into Conventional Commits. Trigger on phrases like "commit my changes", "커밋해줘", "커밋 분리", "make commits", "/conventional-commit", or whenever the user wants to turn current changes into Conventional Commit-style commits. For commit + push use `conventional-commit-push`; for rewriting non-Conventional commit history use `conventional-commit-rewrite`.
Used in Git development when you need to abandon current attempts and roll back to a historical commit. It automatically archives the current state to the archive/ branch and establishes bidirectional links (source and target) in ARCHIVE.md to ensure traceability of the development decision flow. Suitable for scenarios requiring safe rollback while retaining the context of failed attempts.
Update the title and body of one or more pull requests.
Applicable when you need to resolve ongoing git merge/rebase conflicts.
Use when writing a mission report to the gateway DB from any operator mission.
Manage and synchronize multiple Git repositories across workspace-hub. Use for bulk git operations, repository status checks, branch management, and coordinated commits across 26+ repositories.