메뉴
Collect user feedback about the Agentic Meta Project and file it. Use when the user says "feedback", "report a bug", "file an issue", or wants to report friction, suggestions, or feature requests. Files as a GitHub issue if gh CLI is available, otherwise writes a local report.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Run cleanroom build+test from build tree, install tree, and relocated install tree.
Create a structured decision workflow for design-heavy repositories. Use when the user needs to compare options with tradeoff analysis, assign a decision owner, and track consequences. Produces a DW-NNN document with options, pros, cons, and tradeoff analysis.
Turn a rough design discussion into a structured written brief. Use when the user has unstructured notes, chat logs, or conversation fragments that need to become a clear document with positions, open questions, and decision points.
Synchronize documentation indices and cross-references. Use after adding, renaming, moving, or deleting documentation files. Finds orphaned docs, stale links, and broken cross-references, then fixes them and reports changes.
Package a locally discovered lesson for forwarding to the Agentic Meta Project. Use after a session review identifies a finding that generalizes beyond this project -- a template gap, missing skill, or structural issue that would affect any project using the system.
Create or manage a bug-fix workflow packet. Use when the user reports a bug, says "fix this bug", or needs a structured workflow for diagnosing and resolving a defect. Emphasizes reproduction, root cause analysis, minimal fix, and regression testing.
| name | feedback |
| description | Collect user feedback about the Agentic Meta Project and file it. Use when the user says "feedback", "report a bug", "file an issue", or wants to report friction, suggestions, or feature requests. Files as a GitHub issue if gh CLI is available, otherwise writes a local report. |
Provide a structured way for users to report bugs, friction, suggestions, or feature requests back to the meta-project maintainers. This closes the feedback loop between real-world usage and template improvements.
Ask the user for feedback type. Options: bug, friction, suggestion, feature request.
Collect a description. Ask the user to describe the issue. Include:
Gather context. Note the following automatically (ask the user before including project-specific details):
.agents/project.json.Check if gh CLI is available. Run gh auth status to verify.
If gh is available: create a GitHub issue on the meta-project repository with:
[<feedback-type>] <short summary>feedback, <feedback-type>## Feedback Type
<bug | friction | suggestion | feature request>
## Description
<user's description>
## Reproduction Steps
<steps, or "N/A">
## Context
- Amplify version: <version>
- Project type: <type>
- Skills involved: <list or "none">
## Expected Behavior
<what the user expected>
---
Filed via `/feedback` skill.
If gh is not available: write the report to .untracked/feedback/<YYYY-MM-DD>-<summary-slug>.md using the same format. Tell the user where the file is and how to file it manually.
Update feedback index. Append a row to .untracked/feedback/feedback-index.md:
| <YYYY-MM-DD> | <short summary> | <feedback-type> | open | <filename or issue-URL> |
If feedback-index.md does not exist, create it with the header row first.
gh available: a GitHub issue URL.gh unavailable: a local file at .untracked/feedback/<YYYY-MM-DD>-<summary-slug>.md.gh auth status fails, fall back to local file without asking the user to authenticate..untracked/feedback/ does not exist, create it.