원클릭으로 Manus에서 모든 스킬 실행

scitex-dev-linter

스타0

포크0

업데이트2026년 6월 14일 12:41

[WHAT] AST-based linter for reproducible-research Python — 47 built-in rules across 7 categories: STX-I (imports), STX-IO (forbid raw pd.read_csv / np.load / pickle / fig.savefig — use scitex.io.save / scitex.io.load instead), STX-P (path handling — resolve via scitex.path, no hardcoded `/home/...`), STX-PA (plot/axes), and more. [WHEN] User asks to lint scitex code, check scitex conventions, list linter rules, show STX-IO001 meaning, or enforce reproducible-research style; mentions STX-*, scitex-dev linter, scitex conventions, reproducibility lint. [HOW] `scitex-dev linter check <path>` (CLI) or `scitex_dev.linter.check(path)` (Python). Hook integration auto-runs on PreToolUse for Edit/Write.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

scitex-ai

scitex-ai/scitex-dev

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

scitex-dev linter

Interfaces: Python ⭐ · CLI ⭐⭐ · MCP ⭐ · Skills ⭐⭐ · Hook ⭐⭐⭐ (primary) · HTTP —

Code convention checker for SciTeX ecosystem packages.

Installation & import (two equivalent paths)

The same module is reachable via two install paths. Both forms work at runtime; which one a user has depends on their install choice.

# Standalone — pip install scitex-dev
from scitex_dev import linter
scitex_dev.linter.list_rules(...)

# Umbrella — pip install scitex
import scitex.linter
scitex.linter.list_rules(...)

pip install scitex-dev alone does NOT expose the scitex namespace; import scitex.linter raises ModuleNotFoundError. To use the scitex.linter form, also pip install scitex.

See [../../general/02_interface-python-api.md] for the ecosystem-wide rule and empirical verification table.

Sub-skills

Mandatory leaves

01_installation.md — pip install + extras + smoke verify
02_quick-start.md — minimal check-files example
03_python-api.md — top-level Python surface
04_cli-reference.md — scitex-dev linter subcommand summary

Core

06_quick-start.md — basic usage (legacy detail)
07_rule-catalog.md — all built-in rules

Workflows

10_cli-reference.md — CLI commands (legacy detail)
11_mcp-tools.md — MCP tools for AI agents

CLI

scitex-dev linter check [path]
scitex-dev linter list-rules

MCP Tools

Tool	Description
`linter_check`	Check files for convention violations
`linter_check_source`	Check source code string
`linter_list_rules`	List available rules

Environment

20_env-vars.md — SCITEX_* env vars read by scitex-dev linter at runtime

이 저장소의 다른 Skills

같은 저장소

scitexification

scitex-ai/scitex-dev

[WHAT] Scitexification — the verb: translate existing code (a script, a notebook, a small repo, a published-paper supplement) into SciTeX form so it gains the ecosystem's session-managed I/O, scitex-clew evidence binding, publication-quality figures, and project structure. Single source of truth for the migration act itself, package-agnostic; per-package patterns delegate to the per-pkg SKILL.md, and Clew-specific specialization layers on top of this skill via `scientific/04_clew_*`. [WHEN] You have existing code that works and want to bring it into the SciTeX ecosystem with minimal rewrite, OR an agent is asked to translate a research capsule, paper supplement, or one-off notebook into a SciTeX project. Load this skill BEFORE picking the per-chapter topic. [HOW] Read this SKILL.md first to orient on the 5-stage translation arc; then drill into the topic chapter you need next (`01_io-patterns`, `02_session-config`, `03_plt-patterns`, `04_repro-clew`, `05_naming-and-numbering`). Per-package details (full stx.i

2026-06-200

scientific

scitex-ai/scitex-dev

[WHAT] Scientific-methodology skills for the SciTeX ecosystem — publication-quality figures, statistics, experiment reproducibility. Distinct from `general/` (which covers package engineering) and per-package skills (which cover package-specific APIs). Load when authoring analysis scripts, preparing figures for manuscripts, or checking scientific rigour of ecosystem output. [WHEN] Authoring analysis scripts, preparing figures or PDF reports for manuscripts, or auditing scientific outputs of any ecosystem package. [HOW] Read SKILL.md as the index, then drill into the numbered sub-skill leaves (`01_figures_*`, `02_research-project_*`, `03_reporting_*`) for the relevant topic.

2026-06-200

scitex-dev

scitex-ai/scitex-dev

[WHAT] Developer utilities for maintaining the whole SciTeX ecosystem across ~15 packages — version audit and mismatch fixing, editable-install sync, per-host git pull/commit/diff via SSH, bulk rename across files + contents + directories + symlinks (with git-safety guards), aggregated docs search across all packages, a Result/ErrorCode envelope shared by CLI + MCP, DevConfig/HostConfig, a local +… [WHEN] Use whenever the user asks to "list scitex versions", "check for version mismatches", "fix version drift", "rename old_name → new_name across all files", "sync my changes to the HPC / laptop / servers", "run tests on the HPC via Slurm", "poll my sbatch job", "fetch HPC test output", "search the docs for save_fig", "commit remote changes on gpu01", "pull all repos", "audit the ecosystem before a… [HOW] See sub-skills index for entry points.

2026-06-170

general

scitex-ai/scitex-dev

[WHAT] Canonical engineering standards every `scitex-*` package and research project must follow — 3-layer architecture cascade, dependency/version pinning, local-state directory layout (`~/.scitex/<pkg-short>/` and `<project>/.scitex/<pkg-short>/`), repo layout (src/tests/scripts/examples), the five interfaces (Python API → CLI → MCP → Skills → optional HTTP) with their delegation rules and the noun-verb CLI convention, README/Sphinx docs, version-control workflow plus `scitex-dev ecosystem …` release automation, skill-authoring rules (layout, editable-vs-wheel install, public-vs-private), and the periodic quality checklist. Use as the single entry point for creating, auditing, reviewing, or releasing any SciTeX package. [WHEN] Creating, auditing, reviewing, or releasing any SciTeX package, or onboarding a research repo to ecosystem standards. [HOW] Read SKILL.md as the index, then drill into the per-category sub-dirs (`01_ecosystem/`, `02_package/`, `03_interface/`, `04_docs/`, `05_development/`, `09_qualit

2026-06-140

playwright-cli

scitex-ai/scitex-dev

ALWAYS invoke this skill when the user wants to navigate websites, fill forms, take screenshots, test web UIs, extract page data, or debug frontend behavior. Do not spawn browser automation without loading this skill first.

2026-05-020

skill-creator

scitex-ai/scitex-dev

ALWAYS invoke this skill when the user creates, edits, optimizes, benchmarks, or evaluates a Claude Code skill, or asks to improve a skill's activation rate. Do not write or modify SKILL.md files without loading this skill first.

2026-05-020

name	scitex-dev-linter
description	[WHAT] AST-based linter for reproducible-research Python — 47 built-in rules across 7 categories: STX-I (imports), STX-IO (forbid raw pd.read_csv / np.load / pickle / fig.savefig — use scitex.io.save / scitex.io.load instead), STX-P (path handling — resolve via scitex.path, no hardcoded `/home/...`), STX-PA (plot/axes), and more. [WHEN] User asks to lint scitex code, check scitex conventions, list linter rules, show STX-IO001 meaning, or enforce reproducible-research style; mentions STX-*, scitex-dev linter, scitex conventions, reproducibility lint. [HOW] `scitex-dev linter check <path>` (CLI) or `scitex_dev.linter.check(path)` (Python). Hook integration auto-runs on PreToolUse for Edit/Write.
tags	["scitex-dev-linter"]
allowed-tools	mcp__scitex__linter_*
primary_interface	hook
interfaces	{"python":1,"cli":2,"mcp":1,"skills":2,"http":0}

scitex-dev linter

Interfaces: Python ⭐ · CLI ⭐⭐ · MCP ⭐ · Skills ⭐⭐ · Hook ⭐⭐⭐ (primary) · HTTP —

Code convention checker for SciTeX ecosystem packages.

Installation & import (two equivalent paths)

The same module is reachable via two install paths. Both forms work at runtime; which one a user has depends on their install choice.

# Standalone — pip install scitex-dev
from scitex_dev import linter
scitex_dev.linter.list_rules(...)

# Umbrella — pip install scitex
import scitex.linter
scitex.linter.list_rules(...)

pip install scitex-dev alone does NOT expose the scitex namespace; import scitex.linter raises ModuleNotFoundError. To use the scitex.linter form, also pip install scitex.

See [../../general/02_interface-python-api.md] for the ecosystem-wide rule and empirical verification table.

Sub-skills

Mandatory leaves

01_installation.md — pip install + extras + smoke verify
02_quick-start.md — minimal check-files example
03_python-api.md — top-level Python surface
04_cli-reference.md — scitex-dev linter subcommand summary

Core

06_quick-start.md — basic usage (legacy detail)
07_rule-catalog.md — all built-in rules

Workflows

10_cli-reference.md — CLI commands (legacy detail)
11_mcp-tools.md — MCP tools for AI agents

CLI

scitex-dev linter check [path]
scitex-dev linter list-rules

MCP Tools

Tool	Description
`linter_check`	Check files for convention violations
`linter_check_source`	Check source code string
`linter_list_rules`	List available rules

Environment

20_env-vars.md — SCITEX_* env vars read by scitex-dev linter at runtime