メニュー
Submit bug reports, feature requests, and plugin requests to aiocean/claude-plugins via GitHub Issues.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Runs an adaptive, project-aware code-review workflow (profile the project, detect its lint tools + conventions, run mechanical + semantic review, consolidate into an LGTM verdict) and carries the Google eng-practices playbook it applies — reviewer (what to look for, when to approve, severity-labeled comments, handling pushback) and PR/CL author (CL descriptions, splitting changelists, responding to comments). Use when reviewing or authoring a PR/MR/CL/diff, running a code review, deciding LGTM or LGTM threshold, authoring a merge request, assessing code health, handling a hotfix review, or replying to review feedback.
Push books/docs and read notes from an Onyx BOOX e-reader account (push.boox.com / send2boox.com) WITHOUT the web UI, via the self-contained `boox.mjs` CLI. Uploads a file to Aliyun OSS, writes a digital_content doc into the device's MESSAGE sync channel, and calls saveAndPush to notify the device — the exact 3-step flow the web app performs. Also lists the push list, lists synced notes, removes pushed items, and shows device online status. Auth = long-lived JWT via BOOX_TOKEN env or a token file.
Capture this session's repeatable process into a reusable SKILL.md file via guided interview.
Turn Claude into a wise, effective teacher whose only goal is to make sure YOU deeply understand the work an AI agent just did — the problem it solved, why that problem existed, the solution and its design decisions, the edge cases it handled, and the broader impact. Incremental and mastery-gated: it has you restate your understanding first, fills the gaps at the depth you ask for (eli5 / eli14 / like-an-intern), shows you the real code, and quizzes you with AskUserQuestion — and it does not conclude until you have demonstrably understood. Use when the AI moved faster than you could follow and you want to catch up before merging. Trigger on "teach me", "help me understand what you did", "make sure I understand this change", "walk me through this", "explain the session", "I don't get it", "why did you do it this way", "quiz me", "eli5 / eli14", "don't let me fall behind", "I want to actually understand this, not just merge it", "catch me up", "bring me up to speed", "I fell behind", "the AI moved too fast".
Architecture decision advisor — guides pattern selection, application, synthesis, and stress-testing for system design, scaling, resilience, and migration decisions.
Look up architecture patterns and concepts via semantic search — read the full article on demand, compare patterns side-by-side, or browse by volume.
SOC 職業分類に基づく
| name | aio-feedback |
| description | Submit bug reports, feature requests, and plugin requests to aiocean/claude-plugins via GitHub Issues. |
| when_to_use | submit feedback, report bug, request feature, request plugin, file issue, bug report, feature request, plugin request, github issue, file a bug |
| argument-hint | [bug | feature | plugin] description |
| effort | low |
which gh 2>/dev/null || echo "NOT INSTALLED — brew install gh"gh auth status 2>/dev/null | grep -q "Logged in" && echo "authenticated" || echo "NOT AUTHENTICATED — run: gh auth login"echo "${CLAUDE_PLUGIN_ROOT}/skills/aio-feedback/scripts"Submit bug reports, feature requests, and plugin requests directly to the aiocean/claude-plugins repository without leaving Claude Code.
SCRIPTS="${CLAUDE_PLUGIN_ROOT}/skills/aio-feedback/scripts"
Ask the user what kind of feedback they want to submit:
| Type | Label | Use for |
|---|---|---|
bug | bug | Something broken or not working as expected |
feature | enhancement | Improvement to an existing plugin |
plugin-request | plugin-request | Request for a new plugin to be added |
Gather from the user:
For bug reports:
For feature requests:
For plugin requests:
Build a markdown body and submit using the script:
bash "$SCRIPTS/feedback-submit.sh" "<type>" "<title>" "<body>"
Bug report body template:
## Plugin
<plugin-name>
## What happened
<description>
## Expected behavior
<expected>
## Steps to reproduce
<steps or "N/A">
Feature request body template:
## Plugin
<plugin-name or "marketplace">
## What I'd like
<description>
## Why
<motivation>
Plugin request body template:
## Proposed plugin
<name>
## What it should do
<description>
## Use cases
<examples>
The script outputs the created issue URL. Share it with the user so they can track their feedback.