Create GitHub pull requests with self-review and automated quality checks.
npx skills add https://github.com/AndreJorgeLopes/devflow --skill create-pr-andrejorgelopes
Please help me install this Agent Skill. Skill: create-pr Source: https://github.com/AndreJorgeLopes/devflow/tree/main/skills/create-pr Command: npx skills add https://github.com/AndreJorgeLopes/devflow --skill create-pr-andrejorgelopes
It solves the problem of submitting pull requests without consistent self-review, automated quality checks, or a well-structured PR description that makes review easier.
Ask to create a pull request for your current feature branch with devflow-driven self-review and checks.
High-intent search queries and answers about installing and using this skill.
To create a GitHub pull request with automated code review checks, you need a workflow that runs devflow checks or fallback lint, build, and test commands before publishing. This enforces fail-stop behavior to prevent submitting PRs with failing quality gates.
The best way to structure a pull request description is using a conventional title format and a clear body. A reviewer-friendly PR draft should include sections for the summary, specific changes made, testing performed, and the relevant ticket reference.
Yes, you can push a feature branch and create a PR using the GitHub CLI via git push and gh pr create. This process can be automated end-to-end to generate a structured PR template directly from your branch-to-main diff context.
If your pre-PR quality checks fail on a feature branch, you should fix the issues before proceeding. Guardrail-first PR creation prevents publishing when checks fail unless explicitly approved, ensuring code review standards are maintained.
To perform a self-review before creating a pull request, collect your git log and diff context to perform a structured self-audit. Running devflow code review checks validates your changes against quality gates before you finalize the PR draft.
You should split a large git diff before submitting a pull request when the branch-to-main changes become too massive for effective code review. Automated dev workflow tools can suggest splitting large diffs to ensure your PR remains manageable and reviewer-friendly.
yellow-seedIdentify and summarize differences between the current Git branch and its remote base branch.
jimmymalhanAutomate post-merge branch cleanup, inventory refreshes, and regression checks.
panaminiRun build, type-check, lint, tests, security scans, and diff review for PR readiness.
brivaroCreate GitHub Pull Requests with conventional commits via the GitHub CLI.
