stata-lint
Run static analysis on a Stata .do or .ado file and report style and best-practice issues.
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill stata-lint --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
The argument is the absolute path to a `.do` or `.ado` file. 1. Call `stata_inspect_data(action="lint", path=<argument>)`. 2. Display the lint results, grouping issues by severity or type: - Line number and issue description for each finding - Common issues: use of `cd`, `preserve`/`restore`, `#delimit`, hardcoded paths, long lines, missing `version` statement 3. For each category of issue found,
What does the stata-lint skill do?
Run static analysis on a Stata .do or .ado file and report style and best-practice issues.
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill stata-lint --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Auto-Empirical-Research-Skills, a repository with 3,244 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.