Loading...
Loading...
Found 17 Skills
Create GitHub issues with proper task classification. Classification determines which Skills will be used when working on the issue.
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wants a structured GitHub issue. Supports images/GIFs for visual evidence.
Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.
Create GitHub Issue for feature request from specification file using feature_request.yml template.
Use when the user asks to create a GitHub issue from the current conversation context (e.g., "new issue", "create issue", "file an issue", bug/feature request) with a target repo given or auto-detected, and gh CLI is available/authenticated.
Report a bug in the compound-engineering plugin
Create GitHub issues following Pollinations team conventions. Use when asked to create issues, track work, or plan features.
Run /check-posthog, then create GitHub issues for all findings. Each finding becomes a separate, actionable issue with clear acceptance criteria. Invoke for: PostHog audit to issues, analytics backlog creation.
GitHub: Create a new issue in a repository.
Report a bug in the compound-engineering plugin
Create GitHub issues using data-driven templates. Supports any issue type via configurable template configs. Use when the user asks to create a GitHub ticket, issue, or support ticket, or when they want to add a new issue template.