원클릭으로 Manus에서 모든 스킬 실행

시작하기

code-review

스타2

포크2

업데이트2026년 4월 15일 22:47

Instructions for code review on klabis project. Use everytime when code review is requested.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

zabiny

zabiny/klabis

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Code review areas

project best practises
- load backend-patterns skill when reviewing backend code
testing best practises
test coverage of new features, review of tests for changed or removed parts for changes / unnecessary tests
remove dead or unused code
KISS

Additional criteria for HATEOAS API

if API response contains ID referencing another domain object, it must contain also _link record for such domain object
- For example Event detail contains coordinatorId - refenrece to Member object -> it must also define link to referenced object using klabisLinkTo (creating _links.coordinator.href in HAL+JSON response)

Additional criteria for Frontend code

data referenced in HAL response in _links and _affordance are fetched exclusively through useHalResource
- allowed exception: actions in table row

이 저장소의 다른 Skills

같은 저장소

stakeholder-feature-description

zabiny/klabis

Vytváří standalone HTML stránku s product overview popisem konkrétní části aplikace Klabis pro product ownera a stakeholdery. Použij tento skill kdykoli uživatel řekne "vytvoř product overview", "popiš funkcionalitu X pro stakeholdery", "udělej stránku pro product ownera", "vytvoř přehled modulu X", "zdokumentuj feature X pro vedení", nebo chce HTML dokument popisující jak nějaká část Klabisu funguje z byznys pohledu.

2026-06-152

backend-patterns

zabiny/klabis

Backend implementation patterns. Use this skill proactively whenever implementing, modifying, or fixing any backend Java code in this project — including aggregates, domain commands, application services (ports), REST controllers with HATEOAS affordances (klabisLinkTo/klabisAfford), JDBC persistence (memento pattern, repository adapters), domain events and listeners, field-level authorization (@OwnerVisible, @HasAuthority, PatchField), or adding new modules. This is the authoritative source for how Klabis backend code should be structured.

2026-06-012

developer-manual-maintainer

zabiny/klabis

Údržba a aktualizace Klabis developer manuálu v docs/developerManual/. Použij tento skill kdykoli uživatel řekne "vytvoř developer manuál", "aktualizuj manuál", "doplň manuál o X", "podívej se co se změnilo a aktualizuj manuál", "zkontroluj manuál proti kódu", "syncuj manuál se zdrojákem", nebo žádá změnu ve struktuře/obsahu HTML stránek v docs/developerManual/. Použij ho i proaktivně po větším refactoringu v common modulu nebo framework-like částech members modulu (ActingUser, OAuth2 customizace) — manuál by měl popisovat aktuální API. Nepoužívej pro openspec specifikace, byznys-logiku modulů (events, calendar, members business), README ani jinou dokumentaci.

2026-05-122

estimated-kanban-board

zabiny/klabis

Aktualizuje nebo vytváří docs/implementation-status.html — kanban board který porovnává otevřené Github issues v milestonech MVP/core s aktivními OpenSpec specifikacemi a klasifikuje každý tiket jako TODO/IN_PROGRESS/COMPLETED. Aktualizuje i doprovodný markdown docs/implementation-status.md. Použij tento skill kdykoli uživatel řekne "aktualizuj implementation status", "refresh kanban", "update implementation board", "přehodnoť status implementace", "vygeneruj přehled implementace", nebo požádá o přehled kam se s projektem dostali vůči issues. Používej ho proaktivně i když uživatel přímo neřekne "kanban" — pokud chce audit/snapshot rozpracovanosti vůči Github issues, je to tento skill.

2026-04-192

review-collecting-assistant

zabiny/klabis

Asistent pro zpetnou vazbu pri review aplikace

2026-04-082

openspec-writing-guide

zabiny/klabis

Klabis-specific guide for writing OpenSpec specifications. Use this skill whenever writing, reviewing, or rewriting any spec.md file in openspec/specs/. This skill defines the canonical style — user-facing scenarios, UI-context organization, and what belongs in specs vs. non-functional-requirements. Use proactively any time a spec is being created or modified, even if the user doesn't explicitly ask for style guidance.

2026-04-032

name	code-review
description	Instructions for code review on klabis project. Use everytime when code review is requested.
user-invocable	false

Code review areas

project best practises
- load backend-patterns skill when reviewing backend code
testing best practises
test coverage of new features, review of tests for changed or removed parts for changes / unnecessary tests
remove dead or unused code
KISS

Additional criteria for HATEOAS API

if API response contains ID referencing another domain object, it must contain also _link record for such domain object
- For example Event detail contains coordinatorId - refenrece to Member object -> it must also define link to referenced object using klabisLinkTo (creating _links.coordinator.href in HAL+JSON response)

Additional criteria for Frontend code

data referenced in HAL response in _links and _affordance are fetched exclusively through useHalResource
- allowed exception: actions in table row