with one click
create-pr
// Create a well-structured pull request with proper description, labels, and reviewers
// Create a well-structured pull request with proper description, labels, and reviewers
Execute a migration task from a GitHub issue through to a PR, or fix unresolved review comments on an existing migration PR. Reads scope and acceptance criteria from the issue body.
Research a migration task, create a GitHub sub-issue with scope and acceptance criteria, and update the task backlog. Takes a task ID from docs/MIGRATION_TASKS.md, explores the codebase, creates an issue in blockscout/frontend, links it to the parent migration issue, and commits the status update.
| name | create-pr |
| description | Create a well-structured pull request with proper description, labels, and reviewers |
This workflow uses gh to check for existing PRs, fetch issue details, and create the PR. Follow the check-github-cli skill first (ensure gh auth status succeeds; if not, guide the user to install/configure gh and do not proceed). The account needs read access to the repo and write access to create PRs and manage labels.
Create a well-structured pull request with proper description, labels, and reviewers.
Note: In the command output, format all URLs as clickable Markdown links: [Link Text](URL).
git branch --show-current.gh pr list --head <BRANCH> --state open.git status to see uncommitted changes.git add (as appropriate), then git commit -m "..." with a clear message.git push -u origin <BRANCH> (or git push if upstream is already set).git fetch origin main then compare: e.g. git rev-list --left-right --count origin/main...HEAD (expect 0 N for “main has nothing we don’t have”) or merge/rebase if the user wants: git merge origin/main../docs/PULL_REQUEST_TEMPLATE.md as the base. Read it and fill in each section.issue-\d+ (e.g. issue-123), extract the number (e.g. git branch --show-current | grep -oE 'issue-[0-9]+' | grep -oE '[0-9]+'), then:
gh issue view <ISSUE_NUMBER>.Resolves #<ISSUE_NUMBER>../docs/ENVS.md (and the validator/ENVS docs if relevant) to list what changed.NEXT_PUBLIC_VIEWS_TX_GROUPED_FEES environment variable to the documentation."NEXT_PUBLIC_VIEWS_TX_GROUPED_FEES to group transaction fees into one section on the transaction page."NEXT_PUBLIC_VIEWS_TX_ADDITIONAL_FIELDS with set_max_gas_limit to display the maximum gas price set by the transaction sender.""fee reception", for the NEXT_PUBLIC_NETWORK_VERIFICATION_TYPE variable."gh pr create --title "Your descriptive title" --body-file /path/to/body.md (and add --draft if draft)../docs/ENVS.md, add the "ENVs" label: gh pr edit <PR_NUMBER> --add-label "ENVs" (or add labels during gh pr create if your gh version supports it).package.json has changed (check with git diff origin/main -- package.json), add the "dependencies" label.issue-\d+), copy all labels from that issue onto the PR: get labels with gh issue view <ISSUE_NUMBER> --json labels -q '.labels[].name', then add each: gh pr edit <PR_NUMBER> --add-label "<LABEL>".gh pr view --web or the URL printed by gh pr create).