pandas-review
Skill51k starsChanged 2 days agoBSD-3-ClauseView on GitHub
Self-review your own pandas PR (or your local branch before opening one) the way a pandas maintainer would. Prints findings and a verdict in the terminal; never posts to GitHub or edits files.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Who's talking about pandas-dev/pandas
- Data School“4 new time-saving tricks in pandas”YouTube · Jan 25, 2018 · 48k views
- Microsoft Developer“Building the Pandas project in the open with GitHub and Azure Pipelines”YouTube · May 6, 2019 · 20k views
- Microsoft Developer“The pandas project”YouTube · Jan 19, 2023 · 2k views
- GithubTrends“Pandas Replaces $840/yr Tableau — And It's Completely Free #Shorts”YouTube · May 6, 2026 · 1.1k views
- the bumbling biochemist“My favorite resources for learning pandas (python library for analyzing datasets in table formats)”YouTube · May 7, 2023 · 876 views
The biggest 5 of 77 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 77
Talked about on Stack Overflow, YouTube, GitHub, Hacker News and the web (77 times).
On Stack Overflow · 28
- Oct 13, 2017FutureWarning: elementwise comparison failed; returning scalar, but in the future will perform elementwise comparison293 votes
- Jan 27, 2018Pandas groupby with categories with redundant nan47 votes · 5 answers
- Mar 27, 2019python pandas dataframe thread safe?45 votes
- Jul 1, 2022ModuleNotFoundError: No module named '_lzma' when building python using pyenv on macos34 votes
- Jan 2, 2019Pandas : Reading first n rows from parquet file?32 votes
23 more on Stack Overflow
- Aug 3, 2016How to set dtypes by column in pandas DataFrame31 votes
- Oct 23, 2014Plotting datetimeindex on x-axis with matplotlib creates wrong ticks in pandas 0.15 in contrast to 0.1426 votes
- Mar 14, 2019pandas columns correlation with statistical significance23 votes
- May 6, 2020Python FutureWarning: Indexing with multiple keys (implicitly converted to a tuple of keys)22 votes
- Jan 19, 2017Pandas style object with multi-index18 votes · 4 answers
- Dec 4, 2019How to Reference a Pandas Column that has a dot in the name16 votes
- Mar 24, 2019Pandas read_sql() - AttributeError: 'Engine' object has no attribute 'cursor'15 votes
- Sep 28, 2017How to efficiently compute a rolling unique count in a pandas time series?15 votes · 3 answers
- Nov 22, 2016Pandas update sql15 votes
- Jul 11, 2018How to specify flavor of sql in pd.io.sql.get_schema?14 votes · 2 answers
- Dec 11, 2016Pandas: AttributeError: 'module' object has no attribute 'getLogger'14 votes
- Feb 11, 2025numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject13 votes
- Feb 19, 2022pandas pivot_table : NoneType object is not callable13 votes
- Feb 19, 2019Extension dtypes in pandas appear to have a bug with query13 votes · 1 answer
- May 23, 2018TypeError: Type aliases cannot be used with isinstance()13 votes
- May 16, 2018Why are attributes lost after copying a Pandas DataFrame13 votes
- Sep 2, 2020Make pandas plot() show xlabel and xvalues12 votes
- Dec 27, 2019shape vs len for numpy array12 votes
- Mar 28, 2018df.groupby(...).agg(set) produces different result compared to df.groupby(...).agg(lambda x: set(x))12 votes
- Jun 13, 2017Problems importing pandas.plotting12 votes
- Apr 4, 2021UserWarning: Could not import the lzma module. Your installed Python is incomplete11 votes
- Jul 11, 2019Extracting the first day of month of a datetime type column in pandas11 votes
- Oct 2, 2017pandas: slicing along first level of multiindex11 votes · 1 answer
On YouTube · 23
- Jan 25, 20184 new time-saving tricks in pandas — Data School48k views · 85 comments
- May 6, 2019Building the Pandas project in the open with GitHub and Azure Pipelines — Microsoft Developer20k views
- Jan 19, 2023The pandas project — Microsoft Developer2k views · 1 comment
- May 6, 2026Pandas Replaces $840/yr Tableau — And It's Completely Free #Shorts — GithubTrends1.1k views · 4 comments
- May 7, 2023My favorite resources for learning pandas (python library for analyzing datasets in table formats) — the bumbling biochemist876 views · 5 comments
18 more on YouTube
- Jul 22, 2024How to Contribute to Pandas: An Open Source Guide — Code & Contribute with HP554 views · 1 comment
- Apr 6, 2023pandas-dev/pandas - Gource visualisation — Gourcer477 views · 1 comment
- Mar 31, 2023Understanding inplace=True in pandas — The Python Oracle319 views
- May 31, 2022Complete Pandas Data Science Tutorial - Reading CSV , Missing Values, Filtering, Groupby, Plotting.. — Amir Charkhi, PhD270 views · 2 comments
- Aug 22, 202406 How do I create plots in pandas? — IT On Demand191 views
- Aug 15, 2021Pandas Tutorial for Data Science | Introduction - What is Pandas? — Your Code Friend121 views
- Sep 18, 2025Pandas in Python Series for Data Science | Day 4 | Data Science Full Course| Data Science in 30 Days — The Data Key116 views · 3 comments
- Nov 21, 2022What is Pandas? — DataFrame86 views
- Mar 4, 2023Multiple aggregations of the same column using pandas GroupBy.agg() — The Python Oracle61 views
- Dec 23, 2025pandas-dev/pandas - git history visualization — visualsource60 views
- Dec 28, 2020How to use Pandas library in Python — Techweber30 views
- Dec 6, 2023Pandas Extension Arrays with Tom Augspurger — Tobias Macey22 views
- Mar 5, 2023Replacing Pandas or Numpy Nan with a None to use with MysqlDB — The Python Oracle14 views
- Feb 20, 2023Apply pandas function to column to create multiple new columns? — The Python Oracle10 views
- Nov 6, 2026Pandas DataFrames and Series Explained (pandas 3) — Zero to AI Engineer-English8 views · 1 comment
- Oct 29, 2026Monday's report, built by hand. Again? Script it with pandas — The AI Toolbox3 views
- Nov 7, 2026Pandas GroupBy, Merge and Pivot Table Explained — Zero to AI Engineer-English1 view · 3 comments
- Feb 16, 2025how to pandas fast nested for loop for "non numeric" columns? — Emrah KAYA0 views
On GitHub · 14
- Nov 16, 2020BUG: Error installing NumPy via Pip on macOS Big Sur with python from HomeBrew — numpy/numpy63 reactions · 80 comments
- Jan 13, 2019Support type annotations (PEP 484) — numpy/numpydoc58 reactions · 22 comments
- Apr 1, 2024Ecosystem compatibility with numpy 2.0 — numpy/numpy42 reactions · 167 comments
- Aug 13, 2019False positive ``abstract-class-instantiated`` with ``pandas.ExcelWriter`` — pylint-dev/pylint29 reactions · 22 comments
- Mar 6, 2018Cheatsheet request: Pandas (python) — rstacruz/cheatsheets28 reactions
9 more on GitHub
- Oct 19, 2016Improving Jupyter for Spark — jupyter/jupyter26 reactions · 33 comments
- Jun 29, 2020Pandas support for Delta Lake — delta-io/delta20 reactions · 20 comments
- Dec 10, 2020hvPlot as the universal entry point to HoloViz tools — holoviz/hvplot17 reactions · 15 comments
- Mar 5, 2017Data resource renderer — nteract/archived-desktop-app12 reactions · 32 comments
- Dec 3, 2022ENH: enable multiline signatures when too long. — sphinx-doc/sphinx10 reactions · 55 comments
- Feb 12, 2021[REVIEW] Upgrade pandas to 1.2 — NVIDIA/cudf6 reactions · 3 comments
- Mar 17, 2020[REVIEW] Support Pandas 1.0+ — NVIDIA/cudf6 reactions · 33 comments
- Jun 9, 2025pyarrow integration with emmet — materialsproject/emmet5 reactions · 10 comments
- Jun 23, 2020MAINT: remove blacklist/whitelist terms — numpy/numpy5 reactions · 14 comments
On Hacker News · 11
- Apr 3, 2023Pandas 2.0325 points · 111 comments
- Mar 13, 2026OVH forgot they donated documentation hosting to Pandas149 points · 52 comments
- May 5, 2024PDEP-13: The Pandas Logical Type System46 points · 8 comments
- Jan 21, 2026Pandas 3.0.0 Released5 points · 1 comment
- Mar 5, 2020GitHub commit history attributes squashed commit to committer instead of author4 points · 1 comment
6 more on Hacker News
- Mar 10, 2017Pandas Cheat Sheet [pdf]4 points
- Jan 10, 2020pandas v1.0.0rc03 points
- Jan 10, 2020Pandas Pre-Release v1.0.0rc03 points
- Sep 22, 2020Pandas just dropped Python 3.6 support2 points
- Apr 16, 2018Panadas: Plan for dropping Python 2.71 point
- Apr 15, 2018Pandas – Starting January 1, 2019, all releases will be Python 3 only1 point
On the web · 1
- Oct 1, 2024GitHub - Lambert's Blog - Quora — lambert2.quora.com
In this repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 7 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
Read all of them in full, never truncated: diff.patch, any untracked files it lists, and context.md (the PR description, reviews, inline …
- Very specific: line 38
When the code under review is the PR head on GitHub, its changed files are saved under head/.
- Distinctive: line 41
If it reports the branch is behind main, say so.
- Very specific: line 50
Read AGENTS.md at the repo root.
- Distinctive: line 54
Run code when the local build is the code under review: Run the PR's new and changed tests, the existing test files covering the code it …
- Very specific: line 63
Maintainer position: If a maintainer has said the PR shouldn't proceed, the verdict is CLOSE.
- Distinctive: line 89
Don't nit comment length otherwise.
- Distinctive: line 112
Every finding ends with a concrete fix.
- Distinctive: line 133
Keep it concise: findings, not a checklist of what you inspected.
- Distinctive: line 157
If you disagree with a finding, say why on the thread in your own words rather than changing code to satisfy this review.
- Distinctive: line 166
Don't modify files or git state.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review a pandas pull request the way a pandas maintainer would, and report to its author.
Target: $ARGUMENTS
The target is a PR number or URL, a branch name, or nothing (including when the line above
reads literally $ARGUMENTS) to review the current branch with its uncommitted changes.
Review as a maintainer who did not write this code, even if you did. Verify what the PR description, commit messages, and code comments claim instead of taking them on trust. Report only: don't edit files, and don't fix anything during the review. The author decides what to change afterwards.
1. Gather the change and its thread
From the repo root, run
python .agents/skills/pandas-review/scripts/fetch_context.py <target>with no argument for the current branch, and owner:branch for a branch in a fork. It
prints the PR it found (if any), where the code under review is, and the files it wrote.
Read all of them in full, never truncated: diff.patch, any untracked files it lists, and
context.md (the PR description, reviews, inline comments, conversation, the issues the PR
closes or its description references with their reactions, and failing CI jobs with log
excerpts).
- If the script fails, stop and report its error. A failed fetch is unknown, not empty; never review as if the thread were silent.
- When the code under review is the PR head on GitHub, its changed files are saved under
head/. Read any other file at the head withgh api -X GET "repos/pandas-dev/pandas/contents/<path>?ref=<head sha>" -H "Accept: application/vnd.github.raw". - If it reports the branch is behind
main, say so. CI tests the PR merged intomain, so a recent change onmaincan break it there even when it passes locally. - Review verdicts matter most: a maintainer's approval, requested changes, or "I don't think this is worth doing" usually lives there, not inline.
- The thread outranks this file. Where a maintainer on the thread has asked for something that conflicts with the guidance below, follow the maintainer.
2. Investigate
Read AGENTS.md at the repo root. Consult doc/source/development/contributing_codebase.rst
when a question about tests, typing, or backward compatibility comes up. Use Grep/Glob/Read
on the surrounding code to check the change against how the codebase already does things.
Run code when the local build is the code under review. Run the PR's new and changed tests, the existing test files covering the code it touches, and every repro you report, and show real output. If pandas fails to import or build, say so and review from reading alone; don't try to repair the environment.
3. What to look for
In priority order:
- Maintainer position. If a maintainer has said the PR shouldn't proceed, the verdict
is
CLOSE; if they want a different approach,WRONG APPROACH. Skip to section 4 and report only that. If they've said it's blocked on a decision, the verdict isBLOCKED, but review the rest to give the verdict it would get once unblocked. A core maintainer's 👍 reaction on the linked issue counts as buy-in. A/takewith no activity for several days doesn't block anyone. - Unaddressed review comments. For each reviewer request in the thread, check whether
the current diff addresses it or the author replied with a reason. List any that are
neither. Don't draft replies: pandas asks that authors speak for themselves on the
thread (see
doc/source/development/contributing.rst). If the author has already explained on the thread why one of your findings doesn't apply, say so and don't count it toward the verdict, unless the explanation is factually wrong (then say what is wrong with it). - Correctness. Bugs in the diff, and above all regressions: inputs that worked on
mainand break with this PR.- A fix that covers some code paths but leaves sibling paths unfixed is not a defect.
At most mention it as an optional follow-up. Only regressions and wrong results on the
paths the PR claims to fix drive
NEEDS WORK. - A failing CI job the diff causes is a correctness finding; quote the log line.
- A fix that covers some code paths but leaves sibling paths unfixed is not a defect.
At most mention it as an optional follow-up. Only regressions and wrong results on the
paths the PR claims to fix drive
- Necessity, simplicity, brevity. Flag only concrete excess you can point at:
- code, parameters, or tests the fix doesn't need (a guard no input reaches, with the reason; a refactor riding along; a test duplicating an existing one);
- a new helper duplicating existing code (name it at
file:line), a one-caller abstraction that inlines with no loss, or a materially smaller equally-correct approach (sketch it); - the same rationale pasted at several sites, or comments narrating code the PR removed. Don't nit comment length otherwise. Equal-size alternative designs and naming taste are not findings.
- Conventions that commonly come up in review:
- A whatsnew entry describes the user-visible change, not the implementation, and names only public API. A pure refactor gets no entry.
- Tests: module-level functions or an existing class are both fine; so is a new class with a reasonable scope.
Do not report:
- things that are fine ("tests look good", "no whatsnew needed"); silence means no concern;
- PR process or hygiene: template checkboxes, labels, merge readiness;
- CI failures the diff didn't cause (infrastructure, flaky tests, a break already on
main); - drift between the PR description and the diff; review the diff;
- predictions of what a pre-commit hook or CI will catch (the author should run
pre-commitseparately).
4. Output
Open with one or two sentences on what the PR does, then the findings, most important first.
Anchor each localized finding at path:line on its own line, using the line number at
the head of the code under review (not a hunk offset). Use a range when it spans lines. For
diffuse findings (wrong approach, missing coverage) use prose; don't invent an anchor.
Every finding ends with a concrete fix.
pandas/core/indexes/multi.py:1487
`codes` is reused after the early `continue`, so the vectorized path sees the previous
level's array. Fix: move the assignment above the branch.One repro per distinct failure mode: runnable Python, imports included, actual next to expected. Different inputs that fail the same way share one repro. Say in one line whether you executed it; never present predicted output as observed.
import pandas as pd
idx = pd.MultiIndex.from_product([["a", "b"], [1, 2]])
print(idx.get_locs([["a"], [1, 2]]))
# actual: [0]
# expected: [0, 1]Keep it concise: findings, not a checklist of what you inspected.
End with the verdict, the last thing in the output, in a fenced box:
┏━━━━━━━━━━━━━━━━━━━━━━━┓
┃ VERDICT: NEEDS WORK ┃
┗━━━━━━━━━━━━━━━━━━━━━━━┛| Verdict | Means |
LGTM | Ready for maintainer review as-is. |
NITS ONLY | Nothing blocking; the findings are optional. |
NEEDS WORK | Real defects; the approach is sound. |
WRONG APPROACH | Can't be patched into correctness as written. |
BLOCKED | Waiting on a maintainer decision or another PR, not on the author. Add the verdict it would get once unblocked: BLOCKED → NITS ONLY. |
CLOSE | Unlikely to be merged in any form; say why. |
For the author
NITS ONLYclears the bar for review, butLGTMgets reviewed sooner. Fix the nits you agree with and rerun once; then stop, since further reruns surface new optional nits, not blockers.- If you disagree with a finding, say why on the thread in your own words rather than changing code to satisfy this review.
- A green verdict doesn't replace your own review of the change, which pandas requires, and
your PR description still needs the tool, model, and effort you used (see the automated
contributions policy in
contributing.rst).
Hard rules
- Everything stays in the terminal. Never post, comment, review, react, or push on GitHub.
- Don't modify files or git state.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

