repo-feedback-prompt

Create evidence-grounded feedback prompts for external GitHub repositories.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/rbtkhn/grace-mar --skill repo-feedback-prompt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-feedback-prompt
Source: https://github.com/rbtkhn/grace-mar/tree/main/.cursor/skills/repo-feedback-prompt
Command: npx skills add https://github.com/rbtkhn/grace-mar --skill repo-feedback-prompt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users create concise, evidence-based feedback for external GitHub repositories without redundant suggestions, false gap claims, or overly broad requests.

Core Features & Use Cases

  • Repository Gap Verification: Reviews existing documentation and integration surfaces before suggesting improvements.
  • Maintainer-Ready Messaging: Produces respectful issues, direct messages, or email-style prompts focused on high-leverage changes.
  • Use Case: A developer reviewing an open-source project can use this Skill to turn verified observations into a short maintainer feedback request with an optional offer to contribute a PR.

Quick Start

Ask the repo feedback prompt skill to draft a constructive GitHub message based on the repository review notes.

Frequently Asked Questions about repo-feedback-prompt

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

FAQPage Schema
How do I write constructive feedback for an open source GitHub repository?

Constructive GitHub repository feedback requires verifying existing documentation gaps, filtering out redundant suggestions, and applying respectful tone guardrails to ensure maintainer communication is concise and evidence-grounded.

How do I draft a GitHub issue to suggest documentation improvements to maintainers?

Drafting a documentation improvement GitHub issue involves creating structured output templates that focus on high-leverage changes, include verified observations, and optionally offer to contribute a pull request.

What is the best way to communicate with open source maintainers without sounding demanding?

Communicating with open source maintainers requires tone guardrails that filter out overly broad requests and false gap claims, producing respectful messages focused on specific, evidence-based repository improvements.

Can I use structured templates for contribution outreach to external GitHub projects?

Yes, structured output templates support contribution outreach by transforming verified repository review notes into short, maintainer-ready feedback requests with an optional offer to contribute a PR.

How do I avoid submitting false gap claims when reviewing GitHub repository documentation?

Avoiding false gap claims requires a repository gap verification workflow that reviews existing integration surfaces and documentation before suggesting any improvements to maintainers.

When should I not use automated prompts for maintainer communication?

Avoid automated maintainer communication when you lack verified repository review notes, as feedback prompts require evidence-grounded observations to prevent redundant suggestions and overly broad requests.