Skip to content
Skills Library
Programming · Review & audit

code-review

/code-review

Procedure to review a pull request in mixpanel-headless and check each finding before it is posted. Use for every pull request review in this repository.

Licence
MIT
Last repository change
21.10.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
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 21.10.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

Procedure to review a pull request in mixpanel-headless and check each finding before it is posted. Use for every pull request review in this repository.

Original author description

Procedure to review a pull request in mixpanel-headless and check each finding before it is posted. Use for every pull request review in this repository.

How it works

  1. 1. Collect the context
  2. 2. Check each finding before you post it
  3. 3. Check public API changes
  4. 4. Post
Original SKILL.md headings · 49 lines, 319 words
SKILL.md preview
---
name: code-review
description: Procedure to review a pull request in mixpanel-headless and check each finding before it is posted. Use for every pull request review in this repository.
---

# Review procedure for mixpanel-headless

`REVIEW.md` sets the priorities, the evidence a finding needs, the severity
scale, and what not to comment on. This skill is the procedure to apply it.

## 1. Collect the context

1. Read the PR description. List the changed areas: library, CLI, tests,
   conformance, replays, plugin, docs, workflows.
2. For each changed area, read its file in `.github/instructions/`. If that
   file names a folder guide (a `CLAUDE.md` in the folder), read the guide
   too. Not every area has one.
3. Read `REVIEW.md`.

## 2. Check each finding before you post it

1. Find the line that shows the behavior. Do not infer behavior from a
   name, a docstring, or a comment.
2. Where you can, prove the finding:
   - `uv run python -c "..."` for a small behavior check.
   - `uv run pytest <file>::<test> -q` for one focused test. The unit tests
     run offline with mocks.
3. Never run tests under `tests/live/`, and never pass `-m live`. Those
   tests call the real Mixpanel API, and some of them write data.
4. Do not run `just check` or the full test suite. CI runs them.
5. If you cannot support the finding with a line or a check, do not post
   it.

## 3. Check public API changes

For a new or changed public method, type, CLI command or flag, or `MP_*`
variable, compare the code with:

- `uv run mp help <Name>`: the built-in reference must describe the new
  behavior.
- `src/mixpanel_headless/__init__.py`: a new package-level name needs an
  export.
- `CHANGELOG.md`: an entry under `## Unreleased`.
- The matching page in `docs/guide/`.
- For an `MP_*` variable: the environment variable table in `CLAUDE.md`.

## 4. Post

- Give each finding a severity from `REVIEW.md`.
- For a bug, state the input that fails and the wrong result.
- Prefer one precise comment to several speculative ones.
- If the PR is clean, say so.

Versions

RepositoryScoreLicence
This page · mixpanel/mixpanel-headless90MIT
microsoft/aspire100MIT
kdlbs/kandev100AGPL-3.0
dotnet/runtime100MIT
drosam/agents100MIT
ggml-org/llama.cpp100MIT
ShamelesAbyss/Nyx100Apache-2.0
dzhng/jevgrep100MIT
iuliandita/skills100MIT

Database snapshot: 13.11.2026 · package version 5c1189f0b62a (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

  • 100review-pr
    Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "the `review-pr` skill".
  • 100pr
    Pull request descriptions. Use when writing the description of a pull request or merge request.
  • 100review-code
    Review a diff, branch or pull request for real defects, and verify each finding before reporting it. Use this for any request to review, check, look over or assess code changes, or to decide whether a change is safe to merge, including your own changes before you finish.
  • 90install
    Set up Mixpanel for this project — set up an engine for the other Mixpanel skills to use (Mixpanel MCP server, mixpanel-headless Python SDK, or the user's own integration). Use whenever the user asks to set up, install, configure, or connect Mixpanel, switch Mixpanel engine or…
  • 100team-code-review
    Review an agent's own code changes or another contributor's pull request by dispatching specialist agents, verifying every finding, and reporting only evidence-backed issues. Use when the user asks for a code review, PR review, review of a diff, or a multi-agent quality audit.
  • 100review-code
    Review a diff, branch or pull request for correctness, security, performance, tests and readability, with each finding checked against the code and graded blocking, should or nit with a confidence. Use it when asked to review code, before a merge or pull request, and at the end of a plan.

Feedback and reports

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