メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
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.
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.
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.
| name | changelog |
| description | 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. |
The requirement is canonical in .cursorrules ("After ANY code
change…"). This skill only gives the section template, since .cursorrules
specifies what must be present but not the exact layout.
Shell: date +%F → filename changelogs/YYYY-MM-DD.log.uv run pytest -q -m "not scenario" (the tests/e2e/scenarios/ suites are opt-in — see .cursor/08-testing-and-deployment; never run them here). Paste the final summary line into Tests:..cursor/08-testing-and-deployment §Sphinx API Documentation if you added/removed/renamed public Python symbols.## <Title — short, imperative>
Context: <2–6 lines: what triggered the change, what it solves. Reference
user-visible symptoms or technical drivers.>
Changes:
1. <relative/file/path.py>
<one-line description of the change in this file>
2. <relative/file/path.js>
<one-line description>
…
Modified files:
- <relative/file/path.py>
- <relative/file/path.js>
- …
Tests: <e.g. "uv run pytest -q -m 'not scenario' → 312 passed, 0 failed in 18.4s">
Context: and per-file lines..cursor/10 §Error Handling").