Loading...
Loading...
Found 2,778 Skills
Use when user requests autonomous operation across multiple issues. Orchestrates parallel workers, monitors progress, handles SLEEP/WAKE cycles, and works until scope is complete without user intervention.
Use after creating PR - monitor CI pipeline, resolve failures cyclically until green or issue is identified as unresolvable
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or runs /commit-staged or /commit-creator commands.
Intelligently detects when too many files are staged and automatically groups them by feature or functionality using Conventional Commits with user language preference
Archives completed changes and merges specification deltas into living documentation. Use when changes are deployed, ready to archive, or specs need updating after implementation. Triggers include "openspec archive", "archive change", "merge specs", "complete proposal", "update documentation", "finalize spec", "mark as done".
Create a PR for this branch. ALWAYS links related issues and uses closing keywords to auto-close them on merge.
Open source contribution best practices. Creating quality pull requests, writing good issues, following project conventions, and collaborating effectively with maintainers.
Complete spec workflow - generates Run ID, creates isolated worktree, brainstorms requirements, writes lean spec documents that reference constitutions, validates architecture quality, and reports completion
Git workflow patterns for commits, branching, PRs, and history management across heterogeneous repositories. Use when creating commits, managing branches, opening pull requests, or rewriting history. Do not use for non-git implementation tasks or repo-specific release policy decisions without repository documentation.
Generate feature-based and confidentiality-safe English LinkedIn Experience drafts directly from commit messages. Use when asked to write LinkedIn experience text from real commit activity for all-time or a specific date range (`since`/`until` in YYYY-MM-DD), while avoiding repository statistics and internal/confidential implementation details.
Reset the working directory for the next task by ensuring no uncommitted changes exist, then switching to the main branch and pulling latest.
Guany's personal preferences, toolchain, and coding conventions. Use when you need to understand Guany's preferred tech stack, tools, code style, or environment setup. Topics: preferences, toolchain, code style, editor, shell, font, theme, conventions.