← all publishers

vibecodedapps-official

@vibecodedapps-official source repo

Report this profile Claim this profile

• 6 skills
• 0 followers
• 10 hours ago last updated

1. ▌
   Code Review · vibecodedapps-official

   Run a full code review of a pull request, branch, commit, or the working tree by fanning out to the code-review-* sub-reviews in this plugin that the change calls for, verifying the findings, and merging them. Use whenever the user asks for a review, a final pass before merge, or 'what's wrong with this change', even if they do not say 'code review'.
   0 installs
2. ▌
   Code Review Testing · vibecodedapps-official

   Check that every behavior change has a test that fails without it, in the repository's own suite, and that the test asserts behavior rather than implementation. Run by code-review, or alone when the user asks whether a change is tested well enough or what tests to add.
   0 installs
3. ▌
   Code Review Guidelines · vibecodedapps-official

   Audit a change against the rules the repository states for itself in AGENTS.md, AGENTS.override.md, and configured fallbacks such as CLAUDE.md, resolved the way Codex resolves them and quoted exactly. Run by code-review, or alone when the user asks whether a change follows the project's conventions or instruction files.
   0 installs
4. ▌
   Code Review Change Size · vibecodedapps-official

   Judge whether a change is small enough to review well and, if not, propose the first stage to land. Run by code-review, or alone when the user asks whether a pull request should be split or is too big.
   0 installs
5. ▌
   Code Review Correctness · vibecodedapps-official bundle

   The general review pass. Check every changed file for correctness, security, and performance defects with a per-file coverage checklist, confirm each finding in the code, and apply the do-not-report list. Run by code-review, or alone when the user asks for a bug hunt or a review of the logic in a change.
   0 installs
6. ▌
   Code Review Breaking Changes · vibecodedapps-official

   Find changes that break something another party depends on: API contracts, schemas, data mappings, configuration, pipelines, packages, CLIs, stored data, extension manifests, or the logs alarms match on. Run by code-review, or alone when the user asks what a change might break or whether it is backward compatible.
   0 installs