Loading...
Loading...
Found 171 Skills
Create GitHub issues following Pollinations team conventions. Use when asked to create issues, track work, or plan features.
Use when updating GitHub PR title or body. Works around the gh pr edit GraphQL bug caused by GitHub's Projects Classic deprecation.
This skill should be used when the user mentions "gh CLI", "gh command", asks to "view repository info", "trigger workflows", "search GitHub", "manage codespaces", "check PR status", "list issues", or asks about GitHub CLI usage and automation from the command line.
Push commits and create/update pull request
Reviews documentation PRs and provides GitHub PR suggestions. Load when asked to review, suggest changes, or provide feedback on docs content. Covers MDX, frontmatter, style guide, components, and content accuracy.
Create a feature branch in a git worktree from a GitHub issue
Create or update a pull request for the current branch with a summary of all changes.
Search GitHub for repos, code, and usage examples using gh CLI. Capabilities: repo discovery, code search, finding library usage patterns, issue/PR search. Actions: search, find, discover repos/code/examples. Keywords: gh, github, search repos, search code, find examples, how to use library, stars, language filter. Use when: finding repositories, searching code patterns, discovering how libraries are used, exploring open source.
Generates detailed, architect-quality GitHub issues from short instructions. Analyzes the project's actual stack, architecture, and codebase before writing. Detects duplicate issues with intelligent multi-strategy search, validates and creates labels, enforces title conventions, controls scope, and publishes via `gh` CLI with robust error handling. Use this skill whenever the user wants to create a GitHub issue, report a bug, propose a feature, request a refactor, or file any kind of technical issue — even if they just say something brief like "we need to fix the auth flow" or "create an issue for X". Also triggers on: "open an issue", "file a bug", "I want to propose...", "add this to the backlog", "gh issue", or any request that implies creating a trackable work item on GitHub.
Check GitHub Actions workflow status after git push using gh CLI. Reports CI status, identifies failing jobs, and suggests local reproduction commands. Use after "git push", when user asks about CI status, workflow failures, or build results. Use for "check CI", "workflow status", "actions failing", or "build broken". Do NOT use for local linting (use code-linting), debugging test failures locally (use systematic-debugging), or setting up new workflows.
Use when addressing open PR review comments from any reviewer (human or bot) within the current agent session. For a fresh-context-per-comment approach, use ralph-wiggum-loop instead.
GitHub operations skill for gh CLI issue, label, template, and workflow management. Use when requests include: create issue, list issues, apply label, manage templates, check workflow, or gh operations.