Loading...
Loading...
Found 54 Skills
Use this skill when you need to perform Git operations such as committing changes, creating branches, merging, resolving conflicts, managing remotes, or any other Git-related tasks.
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.
Fills Outcomes & Learnings in a plan file and renames it to .done.md.
Comprehensive code review combining PR review, self-review, and quality checks. Supports reviewing PRs by number or comparing branches.
lazygit terminal UI for git. Use for git operations.
Sync .env files from git root repository to worktrees. Use when asked to sync env, copy env, environment file, or when working in a git worktree that is missing a .env file. Automatically detects missing .env in worktrees.
Create or update pull requests for the current branch
Guidance for solving ARC-AGI style pattern recognition tasks that involve git operations (fetching bundles, merging branches) and implementing algorithmic transformations. This skill applies when tasks require merging git branches containing different implementations of pattern-based algorithms, analyzing input-output examples to discover transformation rules, and implementing correct solutions. (project)
[AUTO-INVOKE] MUST be invoked at the START of each new coding session. Covers context management, task strategies, and Foundry-specific workflows. Trigger: beginning of any new conversation or coding session in a Solidity/Foundry project.
Check, create, and manage Git worktrees for parallel branch development. Suitable for scenarios such as batch-creating worktrees based on local branch patterns, placing worktrees in directories at the same level as the repository, avoiding duplicate worktree creation for branches already checked out in other directories, verifying branch-to-worktree path mappings, or preparing isolated workspaces before making modifications across multiple branches.
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
Use when starting task work that needs branch isolation, before planning or coding — creates a worktree branching from current remote main with freshness verification and project setup