yeet

yeet facilitates GitHub-based open source contribution workflows, covering the creation and updating of pull requests and issues, posting comments, and starting discussions. Its guiding principle is semantic analysis over mechanical operation: it aims to understand the intent and context of a change before generating a title, description, or selecting a template, and it keeps all generated content conversational and informal.

The skill covers a set of distinct workflows, each documented in its own reference file that is loaded based on user intent. These include creating and updating PRs, creating and updating issues (with dedicated references for filing bugs against Claude Code, Codex CLI, and Sablier), commenting on issues, and creating discussions. Shared patterns such as authentication validation, admonitions, HEREDOC syntax, semantic analysis, tone, platform normalization, error handling, and file links live in a common reference file.

Before acting, it validates prerequisites. The first required read-only gh command in each workflow doubles as authentication validation, and it prefers a bundled scripts/yeet-context.sh helper to gather repository, template, discussion, label, or issue/PR thread context. Pull request workflows carry extra preconditions: the working tree must be clean or changes committed, the current branch must have commits ahead of the base branch, and remote tracking must be configured.

Use it when contributing to GitHub repositories and you want well-written, context-aware PRs, issues, comments, or discussions rather than boilerplate. It is triggered by phrases like create PR, open PR, yeet a PR, file issue, comment on issue, or start discussion. For detailed GitHub CLI command syntax, flags, and patterns, it defers to a related cli-gh skill, keeping its own focus on workflow orchestration and semantic content generation.