programming

Plugin programming from marketplace ai-skills in CHENyiru3/AI-Skills-Collections. Commands read from the repo's manifest — 3 days ago.

Skills (13)

• designing-python-apis

  Design or review a public Python package API: signatures, return/error contracts, naming and compatibility. Use for explicit interface design or deprecation work; not every internal function edit.

• building-python-clis

  Create, change or test a Python command-line interface, including arguments, streams and exit behavior. Use for Python CLI development with the chosen framework; not merely running a command-line tool.

• improving-python-code-quality

  Fix Python lint/type-checking problems or perform a requested focused maintainability refactor. Use the project’s configured tools and supported Python versions; not a mandatory reconfiguration for every Python edit.

• building-python-communities

  Create or revise Python project contribution, governance, issue/PR templates or maintainer workflows. Use for explicit contributor-experience work; not ordinary code fixes or automatic GitHub messaging.

• documenting-python-libraries

  Write or repair Python package docstrings, usage guides, API references or documentation builds. Use for an explicit package documentation task; a product mention alone does not require Sphinx or deployment setup.

• jupyter

  Inspect, edit, execute or convert a Jupyter .ipynb artifact when notebook-specific cell, output or metadata handling is needed. Reading/editing does not imply executing cells or overwriting the source notebook.

• reviewing-python-libraries

  Assess a Python package for adoption, maintenance or release readiness and report evidence-backed engineering risks. Use for a requested library audit; not a demand to run arbitrary tests or redesign a package during inspection.

• packaging-python-libraries

  Build, inspect or repair an installable Python distribution: metadata, wheels, source archives and package data. Use for packaging work; publication to an index requires that requested scope, and an unrelated pyproject edit does not trigger this workflow.

• optimizing-python-performance

  Profile and improve Python CPU, memory or throughput behavior using representative measurements. Use for an explicit performance investigation or optimization; not mandatory benchmarking for an unrelated edit.

• setting-up-python-libraries

  Scaffold a new Python library or modernize its package structure and selected tooling. Use for explicit setup work; preserve an existing project’s backend, Python support and conventions unless migration is requested.

• managing-python-releases

  Prepare a Python package version/changelog or perform an explicitly requested release. Use for release planning, deprecations and publication workflows; local preparation alone does not authorize tagging, pushing or uploading.

• SQLite

  Design or repair SQLite transactions, concurrency, schema changes, query plans or backups. Use for SQLite-specific behavior and integrity questions; not a blanket migration recommendation for every web application.

• testing-python-libraries

  Design or repair meaningful pytest tests for a Python package, including fixtures, parametrization or property checks. Use for a requested test strategy or regression case; not mandatory coverage infrastructure for every reversible edit.