Skip to content
Skills Library
Programming · Review & audit

bec-code-review

/bec-code-review

Use when A backend diff, pull request or release change needs read-only review for correctness, concurrency, consistency, security, compatibility and test evidence.

Licence
MIT
Last repository change
12.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
6
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when A backend diff, pull request or release change needs read-only review for correctness, concurrency, consistency, security, compatibility and test evidence.

Original author description

Use when A backend diff, pull request or release change needs read-only review for correctness, concurrency, consistency, security, compatibility and test evidence.

How it works

  1. Apply the workflow
  2. Task boundary
  3. Engineering practices
Original SKILL.md headings · 20 lines, 153 words
SKILL.md preview
---
name: bec-code-review
description: "Use when A backend diff, pull request or release change needs read-only review for correctness, concurrency, consistency, security, compatibility and test evidence."
---

# Backend code review

Establish diff scope, owning projects, contracts and actual verification results; read changed code and its callers before reporting risks.

## Apply the workflow

1. Locate the actual project, task boundary and existing contracts; load only the language and domain material needed now.
2. Apply the [specialist checks](references/practice.md), establishing the input evidence before selecting the smallest change.
3. Verify affected behavior with existing repository tools. Explicitly report missing tools, environments or execution; a plan is not a passing result.
4. Deliver scope, specialist decisions, actual verification and remaining risk. A review-only task stays read-only.

## Task boundary

Review is read-only unless fixes are explicitly requested. Do not bury confirmed correctness/security defects under stylistic preferences.

## Engineering practices

Read the [local engineering decisions](references/engineering-practices.md) for this task and follow their links to relevant shared principles. Apply levels and exceptions against actual project contracts; product frontend/backend labels do not constrain language or role.
Files in this package (6)
  • SKILL.md 1 KB
  • references/engineering-practices.md 3 KB
  • references/practice.md 2 KB
  • references/common/engineering-practices.md 12 KB
  • references/common/engineering-practices.rules.json 2 KB
  • references/common/engineering-practices.sources.json 16 KB

Versions

The database has no other skills named bec-code-review.

Database snapshot: 13.11.2026 · package version 4d8364d4575e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 80Code review
    Review a diff or module for correctness, security, regressions, and missing tests. Use when the user asks for a review or before shipping a change.
  • 90code-review
    Review a code diff for correctness, regressions, security, compatibility, and maintainability. Use when asked to review a proposed or completed change.
  • 95pr-review
    Review a PR for correctness, security, code quality, and testing issues. TRIGGER when user asks to review a PR, check PR quality, or give feedback on a PR.
  • 90bec-architecture-design
    Use when Backend module/service boundaries, data ownership, dependency direction, consistency requirements or architecture tradeoffs need design or review.
  • 90review-a-pull-request
    A careful code review of a change, a branch or a pull request: correctness, tests, security, readability, with findings ordered by how much they matter. Use when the owner asks you to review code, a diff, a branch or a PR.
  • 100review
    Review a ClickHouse Pull Request for correctness, safety, performance, and compliance. Use when the user wants to review a PR or diff.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.