feedback-template

Collect template feedback and push it as a standardized PR.

6|2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/i-standard1/yamasaki --skill feedback-template-i-standard1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feedback-template
Source: https://github.com/i-standard1/yamasaki/tree/main/.claude/skills/feedback-template
Command: npx skills add https://github.com/i-standard1/yamasaki --skill feedback-template-i-standard1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

テンプレート開発で発生する要望・不具合の収集と、適切な改善提案を一元化してテンプレートリポジトリに反映する作業を自動化します。

Core Features & Use Cases

  • Feedback collection: ユーザーからの課題や改善案を整理し、PRとして統合する。
  • PR automation: 提案内容をテンプレートリポジトリへPRとして作成・提案する。
  • Use Case: テンプレートの CI 設定やドキュメント不備を修正するためのフィードバックを、再現性のあるPRとして提出する。

Quick Start

テンプレートリポジトリに対して、問題点をフィードバックとしてPRを作成して実行してください。

Frequently Asked Questions about feedback-template

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

FAQPage Schema
How do I automate feedback collection for template repository improvements?

Template feedback collection is automated by scoping user issues to CI, docs, and configuration, then pushing standardized and reproducible change proposals directly to the template repository as a PR.

How do I create a pull request to fix CI configuration issues in a template?

Creating a PR for template CI configuration fixes is handled by submitting your feedback as a PR, which the system then formats with standardized documentation and traceable change proposals for targeted improvements.

Can I use PR automation to propose documentation updates for version control templates?

Yes, PR automation can propose documentation updates for version control templates by scoping feedback to template-related docs and enforcing reproducible change proposals integrated directly into the repository.

What is the best way to standardize pull request formatting for template feedback?

Standardizing pull request formatting for template feedback is achieved by enforcing structured PR formats that ensure traceable documentation and reproducible change proposals across multiple projects.

Does template feedback automation work for targeted improvements across multiple projects?

Template feedback automation works for targeted improvements across multiple projects by scoping feedback to template-related CI, docs, and configuration, enabling consistent and reproducible PR proposals.

When should I not use automated PR proposals for template repository updates?

Automated PR proposals for template repository updates should be avoided when changes fall outside template-related CI, docs, and configuration, as the system scopes feedback specifically to these targeted areas.