baskb

baskb/feedback-studio

Plugin Claude Code

Plugin marketplace listing 1 plugin: feedback-studio.

baskb/feedback-studio

Plugin Claude Code

A local commenting overlay for a website you're building (a static build or your local dev server) or a Markdown file, not public sites you browse. Click or tap any element (or select text) and leave typed or spoken feedback; comments persist to .feedback/, then you tell your agent 'PPF' (Please Process Feedback) to…

baskb/feedback-studio

Hook

Runs after a tool call finishes for Edit, Write, MultiEdit and NotebookEdit tool calls, executing report.mjs via node. From baskb/feedback-studio.

baskb/feedback-studio

Hook

Runs when you submit a prompt, before the agent sees it, executing report.mjs via node. From baskb/feedback-studio.

baskb/feedback-studio

Hook

Runs when the agent finishes a response, executing report.mjs via node. From baskb/feedback-studio.

baskb/feedback-studio

Skill Claude CodeCodex

Instant Feedback Studio playground — serves a bundled sample landing page (a throwaway temp-dir copy) for you to comment on, with a few flaws to find. Starts empty by default (you add the comments); pass --seeded for three worked examples, one per type (fix / change / improve). The fastest way to experience the…

baskb/feedback-studio

Skill Claude CodeCodex

Visual feedback overlay for a local website or Markdown file. The user clicks or selects anything and leaves a typed or spoken comment (even from their phone); you later process those comments, and you can also pin your OWN review comments to elements for the user to approve. Use to review a site or .md, start it…

baskb/feedback-studio

Skill Claude CodeCodex

Turn a feedback round into a shareable review digest — what was asked, what changed (file:line), what was refused or left open and why — written to .feedback/REPORT.md, paste-ready for a PR description, commit message, or Slack update.

baskb/feedback-studio

Skill Claude CodeCodex

Close the loop after processing feedback — re-open the page and prove each resolved comment's change actually landed on the right element. Verified comments get a verdict reply on their thread; failed ones are reopened with an explanation instead of staying silently "resolved".