Skip to content
Back to skills

Development And Testing

ASecurity

"Use statsmodels source-development guidance for Meson/Cython

  • 247 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added September 9, 2026
testingtestingapi

Works with

  • api

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 9, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill development-and-testing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Development And Testing?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Development And Testing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-development-and-testing-a1172c12/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-development-and-testing-a1172c12)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: development-and-testing
description: "Use statsmodels source-development guidance for Meson/Cython
  editable builds, focused pytest selection, docs and example maintenance,
  public API checks, docstring validation, warnings, and contributor
  troubleshooting."
disable-model-invocation: true
metadata:
  disco-role: operating
license: BSD 3-Clause
---

# Development and testing

Use this sub-skill only when the user is editing, reviewing, testing, documenting, packaging, or maintaining a statsmodels source checkout. For ordinary installed-package usage, route to the statistical-modeling sub-skills instead.

## Workflow

1. Determine changed areas: package source, Cython extension, docs/notebooks/examples, tests, public API, warnings, or build metadata.
2. Ensure the checkout is built/installed in editable mode after source or Cython changes. Source builds require compiler, Meson, Cython, NumPy/SciPy, and package dependencies.
3. Run focused tests first, then broader tests only when risk justifies it. Do not run the entire suite by default for small edits.
4. For docs/examples, validate code snippets and generated examples without mutating release or credential-bound tooling.
5. Treat `archive/` as deprecated legacy code and `sandbox/` as experimental unless a task explicitly targets them.

## Read or run

- Read [references/maintenance.md](references/maintenance.md) for editable install, docs/example scripts, API checks, docstring validation, and excluded release tooling.
- Read [references/testing-reference.md](references/testing-reference.md) for focused pytest commands, markers, changed-path mapping, and CI considerations.
- Read [references/troubleshooting.md](references/troubleshooting.md) for build, Cython, pytest plugin, warning, and docs failures.
- Run [scripts/focused_test_plan.py](scripts/focused_test_plan.py) with changed paths to print recommended pytest targets; it does not run tests by default.

## Boundaries

- Do not bundle or run release-key, deploy, or broad CI scripts from this skill.
- Do not tell a future agent to execute original `tools/` scripts as runtime user workflow; this sub-skill describes when such maintainer tools exist and how to replace them with safe commands or focused checks.
- Use the model sub-skills to understand behavior before editing model code.

Files in this skill

  • SKILL.md2.3 KB
  • references/maintenance.md2.1 KB
  • references/testing-reference.md2 KB
  • references/troubleshooting.md1.3 KB
  • scripts/focused_test_plan.py2.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.