commit-and-pr

Commit staged changes, create PRs against develop, and monitor CI status.

1|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/JDenn0514/surveycore --skill commit-and-pr-jdenn0514
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-and-pr
Source: https://github.com/JDenn0514/surveycore/tree/main/.claude/skills/commit-and-pr
Command: npx skills add https://github.com/JDenn0514/surveycore --skill commit-and-pr-jdenn0514

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the PR workflow by automatically committing staged changes, opening a PR against develop, and monitoring CI — enabling teams to manage feature-branch work with minimal manual intervention. It provides a read-only commit workflow and does not edit or create R source or test files; use r-implement for code changes instead.

Core Features & Use Cases

  • Automated PR creation on develop-tracked branches when users trigger commit-and-pr
  • CI monitoring and handoff for failed or passed runs
  • Guardrails to ensure no direct code edits by the agent, with clear handoff prompts for user intervention

Quick Start

Instruct the agent to commit staged changes, open a PR against develop, and start CI monitoring for the resulting feature branch.

Frequently Asked Questions about commit-and-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request creation against develop from staged changes?

To automate pull request creation, this Skill commits staged changes and opens a PR against the develop branch. It then monitors CI status to guide your next collaborative development steps.

Can I use this to edit R source files or test files during the commit workflow?

No, you cannot use this to edit R source or test files. The workflow is strictly read-only for code edits, providing guardrails and clear handoff prompts for user intervention instead.

What is the best way to monitor CI checks for feature branches?

The best way to monitor CI checks is triggering an automated PR workflow. This Skill tracks CI status for feature branches and hands off passed or failed runs for review.

Does the automated GitHub commit workflow support direct code reviews?

The GitHub commit workflow supports collaborative code reviews by opening PRs against develop. It does not make direct code edits, requiring users to manually review and update source files.

When do I need an automated PR workflow for feature branches?

You need an automated PR workflow for feature branches when code updates are not made directly by the agent. It streamlines collaborative development requiring changes to be reviewed via PRs.