Auto-generated tile from GitHub (10 skills)
92
94%
Does it follow best practices?
Impact
92%
1.16xAverage score across 44 eval scenarios
Advisory
Suggest reviewing before use
A development team at a mid-size SaaS company has recently adopted a stricter branching strategy. Feature work is done on short-lived branches off main, and every merge must go through a pull request review with CI passing before it can be merged. The team is tired of manually opening PRs through the browser and losing track of whether CI has passed — developers sometimes merge too early because they forgot to check.
The team wants a shell script (submit-pr.sh) that automates the full PR submission workflow: it should squash local work into clean commits, push the branch, open the PR against main with a proper description, and then wait for the CI pipeline to report back before exiting. The script will be wired into the team's local developer tooling so it needs to be robust and produce clear output at each step.
You are working in a Git repository that has main as its default branch. The current working branch is feature/user-notifications. Assume CI is configured on this repository and will run automatically when the PR is opened. The script does not need to handle every edge case — focus on the happy path, but make it correct.
Produce the following files:
submit-pr.sh — the automation script that performs the full workflowpr-description-template.md — the PR body template the script will use as a starting point for the PR descriptionThe script should be executable and well-structured. It should print progress messages to the user at key steps. The PR description should include at minimum a summary section and a brief description of what the branch changes.
There is no need to implement actual application code — the focus is entirely on the git and GitHub automation workflow.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
scenario-36
scenario-37
scenario-38
scenario-39
scenario-40
scenario-41
scenario-42
scenario-43
scenario-44
skills
documentation
fastify
init
linting-neostandard-eslint9
node
nodejs-core
rules
oauth
octocat
snipgrapher