← all publishers

acevinh

@acevinh source repo

4 published skills

  1. Jarvis Tester · acevinh bundle
    The app's QA tester — four modes: RUN (drive the running app in a real browser, find bugs, log every case + verdict + evidence to a ledger in `docs/testing/`), RE-RUN (only the non-passing rows of an existing ledger), COLD START (no ledger, vague ask: read the code, open the screen, author cases while testing), LOG (you are another skill that just changed behaviour: append ONE line to `docs/testing/inbox.md` and stop). Never edits application source. Read before touching `docs/testing/`. Triggers on "jarvis tester", "javis tester", "test cho anh", "test feat X", "test lại", "QA", "regression", "smoke test", "kiểm tra lại feat", "note lại để test sau", "cần test end to end", or any request to verify that something actually works.
    0 installs
  2. Scan Todo Run · acevinh bundle
    DEFAULT router for real work: scan → classify → match existing patterns → plan with self-critique → TODO → implement → dispatch parallel slices → verify-debug loop. Use when the task touches >3 files, spans more than one repo or package, names no files, or the root cause is not yet known. Triggers on scan, todo, fix bug, implement feature, refactor, add tab/button/column, edit UI, 'similar to X', 'tương tự như', 'triển khai', 'update lại', 'chỉnh sửa', 'làm tiếp', or a design image / URL to test. Only ≤3 already-named files go to quick-fix. Answers in Vietnamese when the user writes Vietnamese.
    0 installs
  3. Convention Review · acevinh
    Review a diff against THIS repo's OWN written rules — CONVENTIONS.md / CLAUDE.md / CONTRIBUTING.md read at runtime, never a memorized rule set — plus correctness, before calling work done. Reports most-severe first with file:line, the section actually read, and a concrete fix. Triggers on review, soát/soát lại, check diff, "review giúp", "check convention", code review, "trước khi done", or after finishing a feature/bugfix.
    0 installs
  4. Quick Fix · acevinh
    Small code task where the user ALREADY NAMED ≤3 files: bug fix, UI tweak, add a button/column/filter, small refactor. Scan only what they gave you, implement, verify. Triggers on fix, chỉnh, sửa, thêm, bỏ, update, 'small change', 'chỉnh lại', 'sửa giúp', 'thêm cho tôi', 'bỏ cái này', 'update lại', a pasted error with a file path, or 1-3 file paths plus a short instruction. Boundary: no files named, >3 files, spans multiple packages/repos, or unknown root cause → escalate to a full scan-and-plan workflow instead. File count decides, not how small it feels.
    0 installs