iterate-pr
Iterate on a PR until CI passes and feedback is addressed. Use when fixing CI failures, addressing review comments, or continuously improving a PR until all checks are green. Automates the feedback-fix-push cyc...
Browse published AI skills maintained by sontek. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
8Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Iterate on a PR until CI passes and feedback is addressed. Use when fixing CI failures, addressing review comments, or continuously improving a PR until all checks are green. Automates the feedback-fix-push cyc...
Create git branches following naming conventions. Use when creating new feature branches, bug fix branches, or any branch for development work. Defines the branch naming standards used across commit and PR skil...
Perform code reviews following engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.
Remove AI-generated code slop from a branch. Use when cleaning up AI-generated code, removing unnecessary comments, defensive checks, or type casts. Checks diff against main and fixes style inconsistencies.
Create structured implementation plans for complex features, refactoring, or multi-phase work. MUST be used when user asks to "create a plan" or "make an implementation plan" or work requires multiple distinct...
Create pull requests following good conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Emphasizes concise, helpful descriptions that respect reviewers' time.
Create commit messages following good conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits and best practices.
Find bugs, security vulnerabilities, and code quality issues in branch changes. Use when reviewing code for bugs, security issues, or quality problems. Thorough but concise reporting.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.