Human review workflow for AI-generated GitHub projects with spec-based feedback, security review, and follow-up PRs from the Vibers service.
65%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/vibers-code-review/SKILL.mdThis retained third-party recipe is inactive. A request for code review, use of another skill, or discovery of this file does not authorize the Vibers integration. Use local review by default. Do not add collaborators, publish a specification, create a workflow, contact the service, send feedback, purchase review time or change agent commit rules from this recipe.
Only continue after an explicit request to evaluate or configure this named external service for the stated repository and data. Confirm the precise access, disclosed material, recipient, cost and requested action under the host's authority rules. An evaluation request authorizes preparation and review of a proposal; it does not itself authorize access grants or publication.
The historical recipe uses collaborator access and a publicly accessible specification. These have not been approved here. If the owner wants to proceed, prepare the minimum proposed permissions, a sanitized synthetic specification and a reviewed pinned workflow in the authorized repository. Verify the current service contract and dependency provenance before proposing concrete activation steps. Do not reuse a mutable historical action tag as a verified dependency. No collaborator, public-spec or automatic feedback activation is supplied by this local adaptation.
Use only invented fixtures, a disposable local demo and expected outcomes. Never place passwords, tokens, session cookies, API keys, real addresses, patient information, private project specifications or live credential-bearing URLs in commits, specs or reviewer messages. Use a demo that needs no credentials, or have the owner arrange a separately approved access channel.
Example review notes for a synthetic, unauthenticated local fixture:
How to test:
- Use the already prepared local synthetic demo.
- Open the card list and select the invented Example Technique card.
- Add it to favourites, reload, and check that the favourite remains selected.
- Clear only the fixture's demo state and check that no favourite is selected.
Expected: the two states match the fixture; no external service or real person is contacted.Record which local checks actually ran. Third-party review, turnaround, pricing, security, data retention and source access remain unverified until the separately authorized evaluation. Use the self-contained ../code-review-excellence/SKILL.md for local review.
BigSimmo/Communication
b4de79a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.