ワンクリックでManusで任意のスキルを実行

refactoring

スター190

フォーク36

更新日2026年4月25日 07:09

Use when the user asks to "refactor", restructure, clean up, simplify, deduplicate, extract, or reorganize code. Enforces the Martin Fowler discipline defined in src/.coding_rules.md and .cursor/08-testing-and-deployment.mdc.

インストール

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

Manusで実行

ソース

databrickslabs

databrickslabs/ontobricks

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

ダウンロード

Manusで実行

OntoBricks refactoring

"Refactor" = the Martin Fowler definition. The canonical guides are src/.coding_rules.md (long-form) and .cursor/08-testing-and-deployment.mdc §Working Style for Refactoring (the 5-step procedure). Read those first; this skill only sequences the work.

Procedure

For every refactor request, follow the 5 steps from .cursor/08:

Summarize the relevant module/function (1–3 sentences).
List code smells, mapping each to a named refactoring (Fowler catalog).
Propose an ordered plan (2–5 steps).
Apply in small, reviewable chunks — one route, one method, one file at a time.
After each chunk: name the refactorings applied, explain the structural improvement, list remaining smells.

Run uv run pytest -q between chunks for non-trivial sequences. Behavior must stay identical — see src/.coding_rules.md §1.1.

Smell → refactoring quick lookup

The full table lives in .cursor/05-code-style-and-structure §Code Smells and src/.coding_rules.md §2. The few I reach for most often:

Smell	Refactoring
Long route handler	Extract Method into the matching `back/objects/` class
Legacy `service.py`	Move Function + delete `service.py` once empty
Repeated try/except → JSON envelope	Extract Function or rely on the global handler
Long parameter list / data clump	Introduce Parameter Object (Pydantic / `@dataclass`)
Magic strings/codes	Replace Magic Number with Symbolic Constant in `constants.py`
God service	Extract Class by domain + Move Function
Module-level functions sharing state	Convert to a class (one public class per file, PascalCase)

Don't

Don't bundle behavioural changes with a refactor — separate commits.
Don't rename a public class/method without a backward-compat wrapper in __init__.py (.cursor/07 §__init__.py Conventions).
Don't skip the changelog (changelog skill).

このリポジトリの他の Skills

同じリポジトリ

deploy

databrickslabs/ontobricks

Use when the user asks to deploy, ship, release, or push OntoBricks to Databricks. Wraps the Databricks Asset Bundle deploy for the FastAPI app and the MCP server, with the bootstrap-perms safety net described in README.md.

2026-06-30190

changelog

databrickslabs/ontobricks

Use after any code change (feature, fix, refactor, review fixup) to update /changelogs/YYYY-MM-DD.log and run the test suite. Mandatory post-change routine — see .cursorrules.

2026-06-29190

code-review

databrickslabs/ontobricks

Use when the user asks for a code review, asks to "review the code", or requests review of a feature/PR/branch. Runs the OntoBricks review checklist defined in .cursorrules.

2026-06-29190

ai-feature

databrickslabs/ontobricks

Use when the user adds, changes, or refactors an LLM agent under src/agents/ — or anything that goes through Foundation Model API or an MLflow-traced LLM call. Mandatory under CNS §3.5 and .cursor/12-ai-feature-lifecycle.mdc. Walks the SPEC → dataset → eval-harness → impl → re-eval sequence.

2026-06-03190

adding-subpackage

databrickslabs/ontobricks

Use when adding a new subpackage under back/core/, back/objects/, or agents/ — e.g. a new graph DB engine, W3C parser, industry importer, reasoning module, or domain class. Enforces the checklist defined in .cursor/07-project-conventions.mdc.

2026-04-25190

OntoBricks refactoring

Procedure

For every refactor request, follow the 5 steps from .cursor/08:

Summarize the relevant module/function (1–3 sentences).

List code smells, mapping each to a named refactoring (Fowler catalog).

Propose an ordered plan (2–5 steps).

Apply in small, reviewable chunks — one route, one method, one file at a time.

After each chunk: name the refactorings applied, explain the structural improvement, list remaining smells.

Run uv run pytest -q between chunks for non-trivial sequences. Behavior must stay identical — see src/.coding_rules.md §1.1.

Smell → refactoring quick lookup

The full table lives in .cursor/05-code-style-and-structure §Code Smells and src/.coding_rules.md §2. The few I reach for most often:

Smell

Refactoring

Long route handler

Extract Method into the matching back/objects/ class

Legacy service.py

Move Function + delete service.py once empty

Repeated try/except → JSON envelope

Extract Function or rely on the global handler

Long parameter list / data clump

Introduce Parameter Object (Pydantic / @dataclass)

Magic strings/codes

Replace Magic Number with Symbolic Constant in constants.py

God service

Extract Class by domain + Move Function

Module-level functions sharing state

Convert to a class (one public class per file, PascalCase)

Don't

Don't bundle behavioural changes with a refactor — separate commits.

Don't rename a public class/method without a backward-compat wrapper in __init__.py (.cursor/07 §__init__.py Conventions).

Don't skip the changelog (changelog skill).

name	refactoring
description	Use when the user asks to "refactor", restructure, clean up, simplify, deduplicate, extract, or reorganize code. Enforces the Martin Fowler discipline defined in src/.coding_rules.md and .cursor/08-testing-and-deployment.mdc.