Loading...
Loading...
Found 429 Skills
Creates git commits. Use this skill whenever the user asks to commit, or whenever you need to commit changes as part of a task.
Detect and resolve Unity C# compilation errors using VSCode diagnostics. Use this skill when Unity projects have compilation errors that need diagnosis and automated fixes. Analyzes errors from VSCode Language Server, proposes solutions based on error patterns, and handles version control conflicts for Unity projects.
Generate concise, descriptive git commit messages following best practices. Use when creating git commits from staged changes, crafting commit messages, or reviewing commit message quality. Use when the user says /commit or asks to create a git commit.
Generate high-quality git commit messages following Conventional Commits and Chris Beams' Seven Rules. Infers WHY from context and provides clear guidance on structure, scope, and body content.
Read the source of the C module we are working on, before we made any changes.
This skill should be used when the user asks to "create a worktree", "new worktree", "worktree for feature", "git worktree", or needs to work on a feature branch in isolation. Handles Rails credential symlinking automatically.
Critical rules for git operations. Enforces git unstage, git undo, and git stash push/apply usage. MUST ALWAYS be applied when performing git operations like staging, unstaging, undoing commits, or stashing changes.
Use when committing code, managing branches, pushing to remote, creating pull requests, or performing version control operations. Conforms to packages/shared/schemas/skill-routing-value-standard.md.
Analyze, plan, and execute Instantly SDK upgrades with breaking change detection. Use when upgrading Instantly SDK versions, detecting deprecations, or migrating to new API versions. Trigger with phrases like "upgrade instantly", "instantly migration", "instantly breaking changes", "update instantly SDK", "analyze instantly version".
Complete contribution workflow using git-town. Create branch → commit → PR → ship. Preflight at every step. TRIGGERS - contribute, feature branch, create PR, submit PR, git-town contribute.
Maintain the local OpenCode mirror for self-reference
Record git activity summary in memory log.