check-feedback
Skill0 starsChanged 5 months agoMITView on GitHub
Check the CURRENT repo's GitHub issues for feedback the owner left, then act on it by following that repo's own feedback pipeline. Use when the user tells the repo's CEO/manager to "check the issues", "check for feedback", or see whether the owner replied on any issue — or when a CEO/manager session should look for owner feedback and process it per the repo's pipeline.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- cjcovell/claude-skillstheir own version, first seen Aug 7, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- cjcovell/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository57 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-mattSkill
- cast-memberSkill
- codebase-designSkill
- content-pipeline-initSkill
- content-pipelineSkill
- data-analystSkill
- decision-mappingSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- draft-asset-promptsSkill
- edit-articleSkill
- fableSkill
- game-concept-interviewSkill
- git-guardrails-claude-codeSkill
- global-guidelinesSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- improve-codebase-architectureSkill
- karpathy-guidelinesSkill
- launch-sessionSkill
- lesson-reviewSkill
- link-claude-skillsSkill
- loop-meSkill
- migrate-to-shoehornSkill
- obsidian-vaultSkill
- opusSkill
- prototypeSkill
- publish-metadataSkill
- resolving-merge-conflictsSkill
- retrieve-lessonsSkill
- reviewSkill
- rotate-sessionSkill
- run-buildSkill
- run-clipsSkill
- scaffold-exercisesSkill
- session-sandboxSkill
- setup-matt-pocock-skillsSkill
- setup-pre-commitSkill
- setup-status-lineSkill
- showrunner-shortSkill
- sonnetSkill
- tddSkill
- teachSkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- verify-outputsSkill
- wrap-allSkill
- wrapSkill
- writing-beatsSkill
- writing-fragmentsSkill
- writing-great-skillsSkill
- writing-shapeSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
If this fails (not a repo, no GitHub remote, or gh not authed), say so and stop — there are no issues to check.
- Distinctive: line 24
Read this repo's CLAUDE.md first — the pipeline (or a pointer to it) is usually there.
- Very specific: line 25
If it points to a dedicated doc (e.g.
- Distinctive: line 27
If you cannot find any documented feedback pipeline, stop and ask the owner where it's defined rather than inventing one.
- Distinctive: line 38
Don't pre-filter with assumptions about labels or markers — surface what the owner actually wrote and let the repo's pipeline decide what …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Go see whether the owner left feedback on this repo's GitHub issues, then handle it by following this repo's own feedback pipeline. This skill only points you at the issues and at the pipeline — it deliberately does not define the pipeline. The repo does.
Operate on the current repo only. One invocation = one repo.
1. Confirm context
Confirm the current directory is a git repo with a GitHub remote and gh is authenticated:
gh repo view --json nameWithOwner -q .nameWithOwnerIf this fails (not a repo, no GitHub remote, or gh not authed), say so and stop — there are no issues to check.
2. Find this repo's feedback pipeline — it is authoritative
The process for interpreting and acting on feedback lives in the repo, not here. Locate it before touching any issue:
- Read this repo's
CLAUDE.mdfirst — the pipeline (or a pointer to it) is usually there. - If it points to a dedicated doc (e.g. a
pipeline.md,feedback.md, or a file underdocs/), read that too.
If you cannot find any documented feedback pipeline, stop and ask the owner where it's defined rather than inventing one. Everything below follows that doc, not this skill.
3. Check the issues
List the open issues and read the ones that may carry owner feedback, including their comment threads:
gh issue list --state open
gh issue view <number> --commentsDon't pre-filter with assumptions about labels or markers — surface what the owner actually wrote and let the repo's pipeline decide what counts as actionable feedback.
4. Act per the repo's pipeline
For each issue where the owner left feedback, do exactly what this repo's pipeline prescribes — respond, relabel, move a stage, open the next piece of work, close it, whatever the pipeline defines. This skill intentionally does not spell out those steps; the repo's doc from step 2 does.
5. Report back
One short summary: which issues had owner feedback, what you did with each per the pipeline, and anything now waiting back on the owner.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.