submit-feedback

Submit be-harness feedback as a pull request to the plugin repository.

1|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/kangmomin/harness-plugins --skill submit-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: submit-feedback
Source: https://github.com/kangmomin/harness-plugins/tree/main/be-harness/skills/submit-feedback
Command: npx skills add https://github.com/kangmomin/harness-plugins --skill submit-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Be-harness feedback collected during workflow phases often ends up isolated or scattered across artifacts. This Skill automates submitting that feedback as a pull request to the plugin repository's community-feedback area, ensuring visibility, traceability, and governance.

Core Features & Use Cases

  • Automatically append user-provided feedback items to the appropriate community-feedback markdown files in the upstream be-harness plugins repo.
  • Create and push a structured PR with a descriptive title and body that reflects the collected feedback, or fall back to local storage when PR submission isn't possible.
  • Supports both generic (universally useful) feedback and project-specific notes, with dry-run and edit capabilities to refine entries before submission.

Quick Start

Submit the collected feedback as a PR to the plugin repository using the defined workflow.

Frequently Asked Questions about submit-feedback

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

FAQPage Schema
How do I submit be-harness feedback as a pull request to the plugin repository?

You can submit both universal and project-specific feedback collected during the be-harness workflow. The Skill appends both types of feedback entries to the appropriate community-feedback markdown files in the upstream plugin repository.

Do I need git and gh installed to automate feedback pull requests?

If PR submission is not possible, the Skill can fall back to local storage to save the collected feedback. This ensures your be-harness feedback is preserved locally even when the automated pull request workflow fails.

Can I review and edit feedback entries before submitting a pull request?

Be-harness feedback collected during workflow phases often ends up isolated or scattered across artifacts. Submitting it as a pull request to the community-feedback area ensures visibility, traceability, and governance for the collected feedback items.

What's the best way to automate community feedback collection into GitHub PRs?

The best way to automate community feedback collection into GitHub PRs is using a Skill that reads plugin.json configuration, appends entries to markdown files, and pushes structured branches. This ensures traceability and governance for be-harness workflow feedback.