wjs-looping-feedback

Solid

Use when the user wants to add an in-site feedback loop to a website repo — a floating "提个建议" button where allowlisted visitors submit suggestions that become a GitHub Issue, which GitHub Actions turns into an automatic code change via Claude Code, auto-merges and deploys, and records on a /_feedback dashboard with one-click revert. Triggers — "给网站加个反馈对话框", "提一句话就自动改网站", "装上反馈闭环", "feedback loop", "/wjs-looping-feedback".

AI & Automation 107 stars 15 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
68
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# wjs-looping-feedback Installs a self-driving feedback loop into any website repo. Runs entirely on the repo owner's own GitHub Actions, authenticated with their Pro/Max OAuth token or their own `ANTHROPIC_API_KEY` — no extra service or backend. ## What it installs 1. A floating feedback button (prefills a GitHub Issue — no backend, no keys client-side). 2. `.github/workflows/feedback.yml` — allowlist gate → Claude Code Action → auto-commit → push to `main` (auto-deploy) → ledger + dashboard update → close issue. 3. `/_feedback` dashboard — every suggestion, what Claude did, commit, status, one-click revert. 4. `.feedback/` runtime: `feedback-lib.mjs`, `feedback-finalize.mjs`, `INSTRUCTIONS.md`, `feedback-ledger.json`, `config.json`. ## How it works visitor clicks button → fills suggestion → prefilled GitHub Issue (label `feedback`) → Actions checks the author is in `FEEDBACK_ALLOWLIST` (else closes the issue) → Claude Code edits the site per `.feedback/INSTRUCTIONS.md` → workflow commits to `main`, updates the ledger + dashboard → the deploy ships it → the issue gets a comment with the commit and a link to `/_feedback`. Revert is the same loop driven by a `revert: #N` issue. ### Deploy triggering — read before you install (common gotcha) The workflow pushes to `main` with the built-in `GITHUB_TOKEN`. Two cases: - **External push-deploy host** (Cloudflare Pages git-connect, Vercel, Netlify): their webhook fires on every push, so the bot's commit deploys automatic...

Details

Author
jianshuo
Repository
jianshuo/claude-skills
Created
2 months ago
Last Updated
3 days ago
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

loopback

Work the Loopback feedback queue — the cross-project bus where real product usage lands as actionable items (pinned UI feedback, backend failures with captured response bodies, UX papercuts, AI-feature feedback with run metadata) and where fixes are written back so pins turn green. Use this whenever the user says "work the feedback queue", "work the loopback queue", "check loopback", "fix the reported feedback", "fix the pins", "what did users report", "triage the feedback", "file feedback", or asks in any words to act on user-reported issues, close reported bugs, or report an observation into the queue — even if they never say "Loopback". Requires the loopback_* MCP tools (or the HTTP /ingest endpoint for filing).

0 Updated today
joshidikshant
AI & Automation Listed

contributing-to-loopover

Use when writing, testing, or preparing ANY code contribution or pull request to the JSONbored/loopover repo — picking/validating an issue, implementing a change, writing tests that pass Codecov, running the local CI gate, predicting the loopover gate, and formatting the commit + PR. loopover reviews PRs ONE-SHOT via the loopover gate (a GitHub App / CI) plus a strict CI suite with Codecov (99% patch coverage, hard); there is no review back-and-forth, so a PR must be correct, fully tested, house-style-compliant, and green before it is pushed. Invoke for any "contribute to / open a PR against / fix a bug in / add a feature to loopover" task.

18 Updated today
JSONbored
AI & Automation Listed

visual-feedback

Use when the user wants to give feedback on a document, concept, design, plan, or report section by section - e.g. asks for a "Review-Seite", "Feedback-Seite", a kommentierbare HTML-Version, "Feedback zu jedem Abschnitt/jeder Box/jedem Element", comment pins in SVG diagrams, or wants to annotate a deliverable and paste the collected feedback back into the chat. Also when retrofitting an existing HTML page so every element accepts comments.

3 Updated 4 days ago
okuegow