From f59c9ee0ab201c99d137a689936dd252c31356f1 Mon Sep 17 00:00:00 2001 From: Donghyun Lee Date: Sat, 10 Jan 2026 18:15:40 +0900 Subject: [PATCH 1/3] feat: create configuration file of 'coderabbit' --- .coderabbit.yaml | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 .coderabbit.yaml diff --git a/.coderabbit.yaml b/.coderabbit.yaml new file mode 100644 index 0000000..02fd590 --- /dev/null +++ b/.coderabbit.yaml @@ -0,0 +1,39 @@ +# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json +language: 'en-US' +early_access: false +reviews: + profile: chill + request_changes_workflow: false + high_level_summary: true + review_status: true + commit_status: true + fail_commit_status: false + collapse_walkthrough: true + changed_files_summary: true + sequence_diagrams: true + estimate_code_review_effort: true + assess_linked_issues: true + related_issues: true + related_prs: true + suggested_labels: true + auto_apply_labels: false + suggested_reviewers: true + auto_assign_reviewers: false + in_progress_fortune: true + poem: false + enable_prompt_for_ai_agents: true + path_filters: + - '!**/*.xml' + - '!**/__generated__/**' + - '!**/generated/**' + - '!**/*.json' + - '!**/*.svg' + - '!**/*.png' + - '!**/*.jpg' + - '!**/*.gif' + - '!**/*.lock' + auto_review: + enabled: true + drafts: false +chat: + auto_reply: true From 117357bf2f66f1d400993e535285e6096cc9b577 Mon Sep 17 00:00:00 2001 From: Donghyun Lee Date: Sat, 10 Jan 2026 18:56:02 +0900 Subject: [PATCH 2/3] chore: update instructions configuration --- .coderabbit.yaml | 58 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 58 insertions(+) diff --git a/.coderabbit.yaml b/.coderabbit.yaml index 02fd590..b948be3 100644 --- a/.coderabbit.yaml +++ b/.coderabbit.yaml @@ -32,6 +32,64 @@ reviews: - '!**/*.jpg' - '!**/*.gif' - '!**/*.lock' + path_instructions: + - path: '**/*.{ts,tsx}' + instructions: | + You are a senior frontend reviewer. + Review this code strictly based on the principles of "easy-to-change code" + from Frontend Fundamentals (Readability, Predictability, Cohesion, Low Coupling). + + ================================ + 1. Readability + ================================ + - Check if the code can be read top-to-bottom like a document. + - Flag places where the reader must jump around to understand logic. + - Suggest extracting logic when multiple contexts are mixed in one function or component. + - Identify magic numbers or strings and suggest meaningful named constants. + - Point out unclear or abbreviated variable/function names. + - Prefer simple control flow over nested or overly clever logic. + + ================================ + 2. Predictability + ================================ + - Verify that function and variable names clearly imply their behavior. + - Ensure functions with similar responsibilities return consistent data shapes. + - Flag hidden side effects (global state mutation, implicit behavior). + - Warn when the same name is used with different meanings across the codebase. + - Suggest making implicit assumptions explicit. + + ================================ + 3. Cohesion + ================================ + - Check whether code that changes together is located together. + - Flag cases where related logic is scattered across multiple files unnecessarily. + - Suggest grouping constants, helpers, and hooks near the domain they belong to. + - Identify components or functions that contain unrelated responsibilities. + - Prefer feature/domain-based structure over technical grouping when applicable. + + ================================ + 4. Coupling + ================================ + - Identify code where a small change would cause wide ripple effects. + - Warn when abstractions increase coupling instead of reducing it. + - Prefer duplication over premature abstraction if it lowers change impact. + - Flag excessive prop drilling and suggest alternative patterns if appropriate. + - Ensure components and functions have a single clear reason to change. + + ================================ + 5. Trade-off Awareness + ================================ + - Do NOT blindly suggest abstraction. + - Always explain why a suggestion improves ease of change. + - If there is a trade-off (readability vs cohesion, duplication vs coupling), + explicitly state it in the review. + + ================================ + 6. Review Tone + ================================ + - Be concise, constructive, and principle-based. + - Avoid stylistic nitpicks unless they affect maintainability. + - Frame feedback as suggestions, not absolute rules. auto_review: enabled: true drafts: false From b00aec6a4452367f8ce93e39f94e4915d1372215 Mon Sep 17 00:00:00 2001 From: Donghyun Lee Date: Sat, 10 Jan 2026 19:15:39 +0900 Subject: [PATCH 3/3] chore: update configurations --- .coderabbit.yaml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.coderabbit.yaml b/.coderabbit.yaml index b948be3..31dd5cc 100644 --- a/.coderabbit.yaml +++ b/.coderabbit.yaml @@ -24,9 +24,9 @@ reviews: enable_prompt_for_ai_agents: true path_filters: - '!**/*.xml' - - '!**/__generated__/**' - - '!**/generated/**' - - '!**/*.json' + - '!**/dist/**' + - '!**/build/**' + - '!**/coverage/**' - '!**/*.svg' - '!**/*.png' - '!**/*.jpg' @@ -92,6 +92,6 @@ reviews: - Frame feedback as suggestions, not absolute rules. auto_review: enabled: true - drafts: false + drafts: true chat: auto_reply: true