skills.rest
JeremyKuhne
JeremyKuhneCOMMUNITY
Explore all skills by this author →
GitHub

address-pr-feedback

Plan pull request edits and gate commits until an explicit publishing verb.

9|1|Updated Jun 6, 2025
Search Tags:#git#workflow#pr#code-review#approval#pull-request
One-click install
npx skills add https://github.com/JeremyKuhne/touki --skill address-pr-feedback-jeremykuhne
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: address-pr-feedback
Source: https://github.com/JeremyKuhne/touki/tree/main/.agents/skills/address-pr-feedback
Command: npx skills add https://github.com/JeremyKuhne/touki --skill address-pr-feedback-jeremykuhne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly and safely address review comments, CI failures, or post-PR feedback without making risky edits or unauthorized commits.

Core Features & Use Cases

  • Pattern-driven approvals: Recognizes explicit publishing verbs to gate commits and pushes.
  • PR-feedback workflow guidance: Helps plan edits in response to reviewer comments and maintain project guidelines.
  • Guardrails and governance: Reiterates rules from AGENTS.md to avoid unsafe actions and keep the PR lifecycle clean.

Quick Start

Propose edits addressing the latest review comments, then wait for an explicit publishing verb before staging, committing, or pushing.

Frequently Asked Questions about address-pr-feedback

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

FAQPage Schema
How do I address pull request feedback without accidentally committing changes?▼

To address PR feedback safely, propose edits guided by review comments and wait for an explicit publishing verb before staging, committing, or pushing any changes to the repository.

What is the safest way to fix CI failures on an existing pull request?▼

Fixing CI failures safely involves planning edits in response to the failures while enforcing safety rules from AGENTS.md, ensuring no unauthorized commits or pushes occur without explicit approval.

How do code review approvals work with git workflow guardrails?▼

Code review approvals gate git actions by recognizing explicit publishing verbs, ensuring that proposed edits addressing reviewer comments are not committed or pushed until explicitly authorized.

Can I apply post-PR follow-up edits while maintaining project guidelines?▼

Yes, you can apply post-PR follow-up edits by planning changes that address feedback while reiterating guardrails and governance rules from AGENTS.md to keep the PR lifecycle clean and safe.

What are the limitations of using pattern-driven approvals for code review edits?▼

The limitation of pattern-driven approvals is that no staging, committing, or pushing occurs without an explicit publishing verb, meaning proposed edits remain local until manually authorized.

Related Skills

Explore More Software Engineering Skills→
zhanglongxiao111zhanglongxiao111
35

using-git-worktrees

Create isolated Git worktrees with safety checks and baseline tests.

Community
Advanced
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
tsunami28tsunami28

create-run-gates

Runs local CI validation gates to detect code analysis and repository compliance failures before pull requests.

Community
Intermediate
navidemadnavidemad

publish

Generate conventional commit messages and GitHub pull request descriptions.

Community
Intermediate