| name | harbor-debug-harbor-core |
| description | Use when debugging, reviewing, or refactoring the harbor/core module. It routes the agent to the module capsule instead of loading the whole repository. |
Harbor Debug Skill: harbor/core
This skill is a thin routing entrypoint generated by Harbor-spec.
It does not replace source code, contracts, tests, or Module Capsule files.
When to use
Use this skill when the task involves:
- debugging the
harbor/core module
- reviewing changes in the
harbor/core module
- refactoring the
harbor/core module
- checking semantic drift in the
harbor/core module
- checking stale or missing module capsule context
Load order
- Read
.harbor/views/modules/harbor/core/module-card.md
- If reviewing code, read
.harbor/views/modules/harbor/core/review-checklist.md
- If debugging failure, read
.harbor/views/modules/harbor/core/debug-playbook.md
- Then inspect only the relevant source files listed in the module card.
Optional docs export may also exist under docs/harbor/modules/<module>/ when enabled.
Required checks
- Contract Impact
- Strictness
- Tests / DDT
- Semantic Drift
- Runtime Safety
- Diary Draft if behavior, schema, or user-visible results change
Before editing
Run or suggest:
harbor module stale harbor/core
If stale, suggest:
harbor module seal harbor/core --write
Do not
- Do not treat this Skill as the source of truth.
- Do not copy stale capsule content into code.
- Do not read the whole repository unless the capsule points to insufficient context.
- Do not modify contracts without checking tests / DDT.
- Do not claim commands were run unless actually executed.
