CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-submit

Create and submit a GitHub PR from the current branch

64

1.92x
Quality

45%

Does it follow best practices?

Impact

96%

1.92x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/pr-submit/SKILL.md
SKILL.md
Quality
Evals
Security

Evaluation results

100%

58%

PR Workflow Runbook

Full PR workflow steps

Criteria
Without context
With context

git status step

100%

100%

git diff step

100%

100%

git log step

100%

100%

Branch prefix decision

30%

100%

New branch creation

100%

100%

Multiple commits for unrelated changes

0%

100%

Push with -u flag

100%

100%

gh pr create usage

100%

100%

Changelog generation step

0%

100%

Changelog commit and push

10%

100%

PR description update step

0%

100%

PR URL returned

33%

100%

88%

14%

Preparing Mixed Changes for a Pull Request

Uncommitted changes handling

Criteria
Without context
With context

git status inspection

100%

100%

git diff inspection

100%

100%

git log inspection

50%

100%

Branch prefix consideration

85%

100%

New branch creation

100%

100%

Identifies unrelated changes

100%

100%

Separate commits for separate concerns

100%

100%

Push with -u flag

0%

100%

gh pr create usage

100%

100%

Post-PR steps mentioned

0%

0%

100%

66%

Submit Feature Branch as Pull Request

Post-PR completion steps

Criteria
Without context
With context

git status in log

100%

100%

git diff in log

100%

100%

git log in log

40%

100%

Branch prefix addressed

37%

100%

Push with -u flag

100%

100%

gh pr create used

100%

100%

Changelog command with PR number

0%

100%

Changelog files committed

0%

100%

Changelog files pushed

0%

100%

PR description update command

0%

100%

PR URL recorded

100%

100%

Post-PR steps ordered correctly

0%

100%

Repository
pipecat-ai/pipecat
Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.