Menu
Create a GitHub pull request following lstk conventions with proper title, description, and ticket references.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Scaffold a new CLI subcommand following lstk patterns. Use when adding a new command to the CLI.
Add a new output event type to the event/sink system. Use when adding a new kind of event for domain-to-UI communication.
Review a PR against lstk architectural patterns and coding conventions. Use when asked to review a pull request.
Scaffold a new Bubble Tea TUI component following lstk's UI patterns. Use when adding a new reusable UI element.
| name | create-pr |
| description | Create a GitHub pull request following lstk conventions with proper title, description, and ticket references. |
| argument-hint | ["base-branch"] |
| disable-model-invocation | true |
| allowed-tools | Bash(git log *), Bash(git diff *), Bash(git branch *), Bash(git push -u origin HEAD), Bash(gh pr create *), Bash(gh label list *), mcp__plugin_linear_linear__get_issue |
Create a PR for the current branch following lstk's conventions.
Run these to understand what's being submitted:
git log main..HEAD --oneline
git diff main...HEAD --stat
git diff main...HEAD
git branch --show-current
If $ARGUMENTS is provided, use it as the base branch instead of main.
Extract the ticket ID from the branch name. The ticket ID is the last path segment, uppercased (e.g., branch user/abc-123 → ticket ABC-123).
Use the Linear MCP tool (mcp__plugin_linear_linear__get_issue) to fetch the ticket details — title and description. Use this context to inform the PR motivation.
Telemetry client, Improve container engine error, Migrate stop command to output event systemUse this structure:
## Motivation
<Why this change is needed. 1-2 sentences.>
## Changes
- Bullet point per meaningful change
- Group related changes together
## Tests
<How this was tested — new tests added, manual verification, etc.>
## Todo
- [ ] Any remaining follow-up items (omit section if none)
Closes TICKET-ID
Rules:
Closes TICKET-ID if the PR fully resolves the issueTowards TICKET-ID if it's a partial contributionAlways apply two labels, based on the size and nature of the change:
semver: patch — bug fixes, dependency/toolchain bumps, internal refactors, and other backward-compatible changes with no new user-facing behavior.semver: minor — new backward-compatible functionality (e.g. a new command or flag).semver: major — breaking changes to existing behavior or interfaces.docs: skip — no user-facing documentation change is required (most dependency/toolchain upgrades, internal refactors).docs: needed — the change adds or alters user-facing behavior that requires documentation updates.This applies to automated PRs too (dependency and toolchain upgrades), which are almost always semver: patch + docs: skip.
If there are uncommitted changes, commit them with a concise message. Do NOT add Co-Authored-By: Claude unless the user explicitly asks for it.
Then push and create the PR with the chosen labels:
git push -u origin HEAD
gh pr create --draft --title "<title>" --body "<body>" --base <base-branch> --label "<semver-label>" --label "<docs-label>"
Return the PR URL when done.