Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
This repository was archived by the owner on Sep 4, 2025. It is now read-only.

Commit51e3fdb

Browse files
Update blog/2024-02-07-mastering-code-review-skill/index.md
Co-authored-by: coderabbitaidev[bot] <142196860+coderabbitaidev[bot]@users.noreply.github.com>
1 parent9c08d02 commit51e3fdb

File tree

1 file changed

+1
-1
lines changed
  • blog/2024-02-07-mastering-code-review-skill

1 file changed

+1
-1
lines changed

‎blog/2024-02-07-mastering-code-review-skill/index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ But the question remains: How does one improve their code review skills? Is it b
2727

2828
Given the specificity of PRs to individual projects, generic feedback often falls short of being genuinely helpful. While coworkers can offer valuable insights, their availability to provide immediate feedback—when the context of the PR code changes is still fresh in your mind—can be limited.
2929

30-
The solution isSelf-Assessment. Assess your Code Review skills and then improve your weaknesses.
30+
The solution is**Self-Assessment**. Assess your Code Review skills and then improve your weaknesses.
3131

3232

3333
##How to Assess Code Review Skills and Improve

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp