GitHub PR Automator FAQs

Question 1

Can I provide specific instructions for the PR description?

Accepted Answer

Yes, you can provide optional instructions after the command (e.g., /pr focus on auth changes) which the AI will use to guide the summary and technical bullet points.

Question 2

What happens if Gitleaks blocks my commit?

Accepted Answer

The skill identifies Gitleaks failures. If the issue is legitimate, it exits so you can fix it; if it's a false positive, it allows you to retry the commit with the --no-verify flag.

Question 3

How does the skill handle working directly on the main branch?

Accepted Answer

If you are on the main or master branch, the skill will automatically stage your changes, generate a new branch name based on the most modified file, and switch branches before committing.

Question 4

Does it support GitHub Pull Request templates?

Accepted Answer

Yes, if your project has a .github/pull_request_template.md file, the skill will prioritize using that template and fill in the appropriate sections.

Question 5

How do I monitor my GitHub Actions with this skill?

Accepted Answer

The skill uses the 'gh run watch' command to block and monitor your CI runs in real-time, providing a pass/fail summary once the checks are complete.

GitHub PR Automator

主要功能

使用场景

GitHub PR Automator

主要功能

使用场景