lint

スター9

フォーク2

更新日2026年5月27日 06:51

Format and lint code across all swiss-ai-hub scopes. Runs make pr-ready (ruff format + ruff check --fix + mdformat + yamlfix), fixes errors, and repeats until clean. Use when user says 'lint', 'format code', 'run pr-ready', 'fix formatting', 'ruff check', 'lint all scopes', or 'format and lint'. Do NOT use for running tests (use /test-scope) or full PR preparation (use /create-pr).

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

bbvch-ai

bbvch-ai/aihub-core

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Lint - Format and Lint All Scopes

Run make pr-ready across the monorepo to format, lint, and fix code. Repeat until zero errors remain.

The stop hook runs make pr-ready automatically at session end. Use this skill mid-session when you need to verify linting is clean before proceeding (e.g., before running tests or reviewing code), or when the stop hook failed and you need to diagnose and fix specific errors.

What make pr-ready Does

The root make pr-ready runs these steps in sequence:

Per-scope make pr-ready for each Python scope (packages/pipeline, packages/core, packages/agent, packages/process, packages/api, packages/bot, packages/web):
- ruff format — auto-format Python code
- ruff check --fix — lint with auto-fix (rules: E pycodestyle, F pyflakes, UP pyupgrade, I isort)
mdformat --number — format all tracked Markdown files (normalize headings, lists, tables)
yamlfix — format all tracked YAML files (except pnpm-lock.yaml)

Frontend scope (packages/web) runs ESLint instead of ruff.

Steps

1. Run make pr-ready from Repo Root

make -C /home/joelbarmettler/projects/aihub/aihub-core pr-ready

2. Review Output for Errors

Ruff auto-fixes most issues. Errors that remain after auto-fix require manual intervention:

Import errors — missing dependency, run uv sync --all-packages
Unused imports/variables — remove them
Unsafe fixes — ruff flags these but won't auto-apply; review and fix manually
Syntax errors — ruff can't auto-fix these; fix the Python syntax manually

3. Fix Errors and Re-run

Fix each error in the reported file. Then re-run:

make -C /home/joelbarmettler/projects/aihub/aihub-core pr-ready

Repeat until the output shows zero errors across all scopes.

4. Run on Specific Scopes (Optional)

If only one scope needs fixing, target it directly:

make -C packages/core pr-ready
make -C packages/api pr-ready
make -C packages/web pr-ready

Ruff Configuration

Each scope's pyproject.toml configures ruff. Key settings:

Line length: 120 characters
Target: Python 3.12+
Rules: E (pycodestyle), F (pyflakes), UP (pyupgrade), I (isort)
Per-file ignores: test files allow unused imports (F401) for fixtures

Troubleshooting

Problem	Solution
`make pr-ready` fails with ModuleNotFoundError	Run `uv sync --all-packages` from workspace root
mdformat fails on deleted file	Stage the deletion with `git rm` first
yamlfix changes too much	Check if the YAML file follows non-standard formatting
ESLint errors in packages/web	Run `pnpm lint --fix` from `packages/web/`

Done When

make pr-ready runs to completion with zero errors across all scopes

このリポジトリの他の Skills

同じリポジトリ

scaffold-agent

bbvch-ai/aihub-core

Generate a new AI agent with all boilerplate (agent class, events, config with form duality, memory, LLM streaming, i18n, BDD tests, entry point). Includes pattern catalog, execution model reference, and implementation checklist. Use when user says "create new agent", "scaffold an agent", "generate agent boilerplate", "add AI agent", "new workflow agent", or "build an agent for X". Do NOT use for debugging agents (use /debug-agent), event infrastructure (use /nats-events), or process orchestration (use /scaffold-process).

2026-08-039

docker-dev

bbvch-ai/aihub-core

Manage the Docker Compose development stack and understand the Jinja2 template-based compose generation system. Covers start/stop/health/logs/restart/status/ports for the dev stack, the template-to-generate-to-commit workflow, and documentation lookup via Context7 MCP. Use when user says 'start docker', 'stop containers', 'check service health', 'show logs', 'restart service', 'docker status', 'which ports are used', 'is the API running', 'regenerate compose', or 'how does docker compose generation work'. Pass action as argument. Do NOT use for reviewing Docker Compose changes (use deployment-reviewer agent) or debugging Dagster pipelines (use /debug-pipeline).

2026-07-029

write-issue

bbvch-ai/aihub-core

Author a new, convention-conformant GitHub issue for bbvch-ai/aihub-core — title format, the In scope / Out of scope / Accepted when body structure, area:* and version labels, sibling and blocked-by cross-references — then create it and add it to the AI-Scrum board (org project 37) with Item Type, Priority, and Status set. Use when user says 'write an issue', 'create a GitHub issue', 'open an issue for X', 'file a bug', 'draft an epic', or 'add a story to the board'. Do NOT use for planning an existing issue's implementation (use plan-issue), breaking an issue into sub-issues (use splice-issue), or creating a PR (use create-pr).

2026-06-259

setup-bot-connection

bbvch-ai/aihub-core

End-to-end guide for setting up a new bot connection in swiss_ai_hub.bot. Covers Azure App Registration, Bot Channels Registration, Teams/Slack channel config, PathEntity creation in bot_paths collection, and DevTunnel for local dev. Use when user says "set up a bot", "connect bot to Teams", "connect bot to Slack", "configure bot channel", "create bot connection", "DevTunnel setup", "bot local development", or "Azure bot registration". Do NOT use for bot handler code scaffolding (use scaffold-bot-handler), bot architecture questions (use bot-framework), or agent debugging (use debug-agent).

2026-06-159

likec4-dsl

bbvch-ai/aihub-core

Use when working with `.c4`/`.likec4` files or LikeC4 CLI/config questions where exact DSL/CLI syntax is required, especially for strict command/snippet-first answers, validate/export flags, predicates `*`/`_`/`**`, deployment snippets, dynamic views, or relationship extension matching.

2026-06-099

audit-frontend

bbvch-ai/aihub-core

Run a comprehensive frontend code audit of the Nuxt 3 admin interface. Checks Pinia-Colada query/mutation patterns, TypeScript strictness, component architecture, SDK freshness, i18n coverage, and Tailwind usage. Use when user says 'audit the frontend', 'check frontend code quality', 'find unused components', 'composable health check', 'pinia-colada audit', 'typescript errors', or 'frontend code review'. Do NOT use for backend API audits (use scaffold-api-endpoint) or bot UI issues (use debug-bot). Reports issues with file locations and severity levels.

2026-05-279

name	lint
description	Format and lint code across all swiss-ai-hub scopes. Runs make pr-ready (ruff format + ruff check --fix + mdformat + yamlfix), fixes errors, and repeats until clean. Use when user says 'lint', 'format code', 'run pr-ready', 'fix formatting', 'ruff check', 'lint all scopes', or 'format and lint'. Do NOT use for running tests (use /test-scope) or full PR preparation (use /create-pr).
allowed-tools	Bash, Read, Edit

Lint - Format and Lint All Scopes

Run make pr-ready across the monorepo to format, lint, and fix code. Repeat until zero errors remain.

What make pr-ready Does

The root make pr-ready runs these steps in sequence:

Per-scope make pr-ready for each Python scope (packages/pipeline, packages/core, packages/agent, packages/process, packages/api, packages/bot, packages/web):
- ruff format — auto-format Python code
- ruff check --fix — lint with auto-fix (rules: E pycodestyle, F pyflakes, UP pyupgrade, I isort)
mdformat --number — format all tracked Markdown files (normalize headings, lists, tables)
yamlfix — format all tracked YAML files (except pnpm-lock.yaml)

Frontend scope (packages/web) runs ESLint instead of ruff.

Steps

1. Run make pr-ready from Repo Root

make -C /home/joelbarmettler/projects/aihub/aihub-core pr-ready

2. Review Output for Errors

Ruff auto-fixes most issues. Errors that remain after auto-fix require manual intervention:

Import errors — missing dependency, run uv sync --all-packages
Unused imports/variables — remove them
Unsafe fixes — ruff flags these but won't auto-apply; review and fix manually
Syntax errors — ruff can't auto-fix these; fix the Python syntax manually

3. Fix Errors and Re-run

Fix each error in the reported file. Then re-run:

make -C /home/joelbarmettler/projects/aihub/aihub-core pr-ready

Repeat until the output shows zero errors across all scopes.

4. Run on Specific Scopes (Optional)

If only one scope needs fixing, target it directly:

make -C packages/core pr-ready
make -C packages/api pr-ready
make -C packages/web pr-ready

Ruff Configuration

Each scope's pyproject.toml configures ruff. Key settings:

Line length: 120 characters
Target: Python 3.12+
Rules: E (pycodestyle), F (pyflakes), UP (pyupgrade), I (isort)
Per-file ignores: test files allow unused imports (F401) for fixtures

Troubleshooting

Problem	Solution
`make pr-ready` fails with ModuleNotFoundError	Run `uv sync --all-packages` from workspace root
mdformat fails on deleted file	Stage the deletion with `git rm` first
yamlfix changes too much	Check if the YAML file follows non-standard formatting
ESLint errors in packages/web	Run `pnpm lint --fix` from `packages/web/`

Done When

make pr-ready runs to completion with zero errors across all scopes