yeet
paulrberg/agent-skills
Create and manage GitHub PRs, issues, and discussions with semantic understanding of intent.
What is yeet?
Yeet facilitates GitHub-based open source contribution workflows including pull requests, issues, and discussions. Use it to create or update PRs/issues, post comments, and start discussions with conversational, context-aware content generation.
- Create pull requests with semantic analysis of changes
- Update existing pull requests and issues
- Post comments on GitHub issues and discussions
- Create and manage GitHub discussions
- Validate authentication and repository context
- Generate conversational titles and descriptions based on intent
How to install yeet
npx skills add https://github.com/paulrberg/agent-skills --skill yeet- GitHub CLI (`gh`) installed and authenticated
- Clean working tree or committed changes (for PR workflows)
- Current branch with commits ahead of base branch (for PR workflows)
- Remote tracking configured (for PR workflows)
How to use yeet
- 1.Identify the workflow intent: create PR, update PR, create issue, update issue, comment, or create discussion
- 2.Run the skill with the appropriate subcommand and options
- 3.Provide context such as branch name, issue number, or discussion topic as needed
- 4.Review the generated content (title, description, comment) before submission
- 5.Confirm to post to GitHub
Use cases
- Opening a PR for a feature branch with auto-generated description
- Filing a bug report as a GitHub issue with proper templates
- Adding a comment to an existing issue thread
- Starting a discussion to gather feedback on a proposal
- Updating PR metadata like title or description after review feedback
- Open source contributors
- Developers managing GitHub workflows
- Teams automating contribution processes
- Anyone filing issues or PRs programmatically
yeet FAQ
Use the GitHub CLI (`gh`) which must be installed and authenticated. The skill validates authentication with read-only `gh` commands at the start of each workflow.
Yes, the skill works with any repository where you have appropriate permissions. Some workflows have repository-specific reference files (e.g., Claude Code, Codex CLI, Sablier), but generic create/update workflows apply universally.
The skill understands the intent and context of your changes rather than just mechanically processing commands. It generates conversational, contextual titles and descriptions based on what you're trying to accomplish.
No. The skill generates conversational descriptions based on your intent and repository context, though you can review and modify before posting.
For PR workflows, your working tree must be clean or changes must be committed. The skill validates this as a prerequisite before proceeding.
Full instructions (SKILL.md)
Source of truth, from paulrberg/agent-skills.
argument-hint: <create-pr|update-pr|create-issue|update-issue|comment-issue|create-discussion> [options] disable-model-invocation: false effort: high name: yeet user-invocable: true description: 'Use for GitHub PR/issue/discussion workflows: create/update PRs or issues, post comments, start discussions; triggers include create/open PR, file/update issue, yeet.'
GitHub Contribution Workflows
Facilitate GitHub-based open source contribution workflows including pull requests, issues, and discussions. Emphasizes semantic analysis over mechanical operations — understand the intent and context of changes before generating titles, descriptions, or selecting templates. All generated content should be conversational and informal.
Prerequisites
Use the first required read-only gh command in each workflow as authentication validation. Prefer scripts/yeet-context.sh when the workflow needs repository, template, discussion, label, or issue/PR thread context.
For pull request workflows, also verify:
- Working tree is clean or changes are committed
- Current branch has commits ahead of the base branch
- Remote tracking is configured
Related Skills
For detailed GitHub CLI command syntax, flags, and patterns, activate the cli-gh skill.
Workflows
Each workflow is fully documented in its reference file. Load the appropriate reference based on user intent.
| Workflow | Trigger | Reference |
|---|---|---|
| Create PR | "create PR", "open PR", "yeet a PR" | references/create-pr.md |
| Update PR | "update PR", "edit PR" | references/update-pr.md |
| Create Issue | "create issue", "file issue" (generic repo) | references/create-issue.md |
| Update Issue | "update issue", "edit issue", "relabel issue" | references/update-issue.md |
| Claude Code Issue | "Claude Code issue", "report bug in CC" | references/issue-claude-code.md |
| Codex CLI Issue | "Codex issue", "report bug in Codex" | references/issue-codex-cli.md |
| Sablier Issue | "Sablier issue", "sablier-labs issue" | references/issue-sablier.md |
| Comment on Issue | "comment on issue", "reply on issue", "post a comment" | references/comment-issue.md |
| Create Discussion | "create discussion", "start discussion" | references/create-discussion.md |
Shared patterns (auth validation, admonitions, HEREDOC syntax, semantic analysis, tone, platform normalization, error handling, file links) are in references/commons.md.
Related skills
More from paulrberg/agent-skills and the wider catalog.
biome-js
This skill should be used when the user asks to "configure Biome", "extend biome config", "set up BiomeJS", "add biome overrides", "biome lint-staged", "fix biome errors", or mentions biome.jsonc, Biome linting, or Biome formatting configuration.
bump-deps
Auto-update Node.js dependencies with smart prompting for major versions and maturity-period support.
bump-release
Automate release versioning, changelogs, commits, and tags for single and monorepo packages.
cli-gh
Automate GitHub operations from the command line: PRs, issues, workflows, and repo management.
payload
Use when working with Payload CMS projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
cms-migration
Use when user wants to migrate content from another CMS (WordPress, Contentful, Strapi, Sanity, Webflow, etc.) to Payload CMS