jianshuo/claude-skills / wjs-looping-feedback
wjs-looping-feedback
VerifiedUse 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".
| File | Kind | Size |
|---|---|---|
| .gitignore | other | 24 B |
| README.md | markdown | 294 B |
| SKILL.md | skill md | 3.1 KB |
| assets/INSTRUCTIONS.md | markdown | 1.4 KB |
| assets/config.sample.json | config | 43 B |
| assets/feedback-finalize.mjs | script | 1.4 KB |
| assets/feedback-ledger.json | config | 20 B |
| assets/feedback-lib.mjs | script | 2.9 KB |
| assets/feedback-widget.html | other | 2.0 KB |
| assets/feedback.yml | config | 5.8 KB |
| package.json | manifest | 144 B |
| references/install.md | markdown | 5.9 KB |
| scripts/detect-site.mjs | script | 803 B |
| tests/detect-site.test.mjs | script | 1.3 KB |
| tests/finalize.test.mjs | script | 3.0 KB |
| tests/lib.test.mjs | script | 3.7 KB |
assets/INSTRUCTIONS.md
View on GitHub# Feedback playbook (run by GitHub Actions)
You are resolving a website feedback issue. The issue title and body are in your prompt.
## If the title matches `revert: #<N>`
1. Open `.feedback/feedback-ledger.json`, find the entry with `issue == <N>`, read its `commit`.
2. Run `git revert --no-commit <commit>`. This stages the inverse change WITHOUT committing
(the workflow commits it for you). If it conflicts, resolve the conflict so the net effect
undoes that commit, and leave the resolution staged/unstaged (do NOT commit).
3. Do NOT edit the ledger or the dashboard, and do NOT commit — the workflow does that next.
4. Stop.
## Otherwise (a normal feedback issue)
1. Implement the smallest change to THIS website that satisfies the request in the issue body.
- Match the site's existing conventions, templates, and style.
- Touch only what the request needs. Do not refactor unrelated code.
2. If the request is unclear, unsafe, or out of scope, make NO change and leave the working
tree clean — the workflow will detect "no changes" and comment back asking for detail.
3. Write a one-line, plain-language summary of what you changed to `.feedback/last-summary.txt`
(Chinese is fine). Example: `把首页标题字号从 1.8rem 调到 2.5rem`.
4. Do NOT edit `.feedback/feedback-ledger.json`, do NOT commit, do NOT push — the workflow
handles ledger, dashboard, commit, and deploy after you finish.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |