Loading...
Loading...
Found 1,822 Skills
Format commit messages following project conventions with commitlint validation. Use when committing changes, writing PR descriptions, or preparing releases.
Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary
Use when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery state
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
Append conversation context to cumulative project history - never overwrites
This skill should be used when the user has a completed implementation plan (plan.md) and is ready to execute the tasks defined therein. Actively uses Agent Teams or subagents to execute batches of independent tasks in parallel, following BDD/TDD principles.
Open source contribution best practices. Creating quality pull requests, writing good issues, following project conventions, and collaborating effectively with maintainers.
Creates commits with conventional format and validation. Use when committing changes or generating commit messages.
OrchestKit skill directory. Use when you want to see available skills or need help.
Visualize planned changes before implementation. Use when reviewing plans, comparing before/after architecture, assessing risk, or analyzing execution order and impact.
Publish a new release of the Feishu plugin. Use when the user asks to release, publish, or cut a new version.
Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository