一键在 Manus 中运行任何 Skill

drift

星标2

分支1

更新时间2026年6月23日 09:38

Dev: check a target (spec / plan / working diff / code) for architectural drift from the rulebook docs/ARCHITECTURE.md — report qualitative deviations citing rule ids, and triage new ones into docs/Debt.md. Usage: /drift <target>

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

OleksandrHavuka

OleksandrHavuka/shadowling

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

相关职业SOC

基于 SOC 职业分类

软件开发工程师计算机与数学类职业·SOC 15-1252

SKILL.md

readonly

name	drift
description	Dev: check a target (spec / plan / working diff / code) for architectural drift from the rulebook docs/ARCHITECTURE.md — report qualitative deviations citing rule ids, and triage new ones into docs/Debt.md. Usage: /drift <target>
allowed-tools	Read Grep Glob Bash(git diff) Bash(git status) Edit

Detect architectural drift: does $ARGUMENTS still fit how shadowling is built? The target is a spec/plan path, the working diff (when omitted or changes), or a code path / ..

Read the rulebook docs/ARCHITECTURE.md (rules carry ids R-<area>-<n>) and the known deviations in docs/Debt.md. Judge the target only against the rules relevant to it. The rulebook is the source of truth — do not restate or reinterpret it here.

Behavior:

Every finding cites its R-id + file:line. No matching rule → not a finding — don't free-associate. Bugs are /code-review; reuse/simplify cleanups are /simplify.
Skip the mechanical rules check.sh/tach already enforce (R-MOD, R-DEV-1/2/4) — this gate is the qualitative layer.
Deviations already in docs/Debt.md are known debt: list them as such, never re-raise as new.
For each genuinely new deviation, ask the user whether to record it. On yes, append it under docs/Debt.md ## Open in the file's format: - [ ] R-<id> — <where>: <what deviates> → <target>. Record only what is confirmed.
Also run the rulebook's rule-gap loop ("How this doc is used" → "Self-improvement"): surface rare rule-gap candidates; on approval append the rule to docs/ARCHITECTURE.md, else drop. Never park a candidate.
Never touch production code. Writes are limited to a confirmed docs/Debt.md append (deviation from an existing rule) and, on approval, a new rule in docs/ARCHITECTURE.md. If the target matches the baseline and no gap surfaces, say so and skip triage.

同仓库更多 Skills

同仓库

anki-sync

OleksandrHavuka/shadowling

Push enriched vocab to Anki Desktop as flashcards and pull review progress back. Usage: /anki-sync

2026-06-212

loot

OleksandrHavuka/shadowling

Add words/terms you're learning, enriched (translation, alternative translations, examples, synonyms, definition) into your native/learning languages. Comma-separated for several at once. Usage: /loot <word>[, <word2>, ...]

2026-06-212

debrief

OleksandrHavuka/shadowling

Review your buffered writing into per-category frequency docs (grammar / rephrasings / idioms / verbs). Usage: /debrief

2026-06-172

shadowling-db

OleksandrHavuka/shadowling

Use whenever you read, query, or mutate shadowling's sqlite database (shadowling.db) — any SELECT/INSERT/UPDATE/DELETE, ad-hoc SQL, dropping/clearing/resetting rows, inspecting data, or checking a migration's result. All DB access goes through a skill entrypoint, a repository method (`models/*`), or `sql.py` — never raw sqlite3. Schema/data-layer changes are NOT made here — they go through an appended migration in appdb.py; this skill only documents that rule and verifies the outcome.

2026-06-172

aha

OleksandrHavuka/shadowling

Explain an expression in the language you're learning that you can't read literally — get a verdict (memorize vs learnable rule) + how to read it, saved to the decode dataset. Usage: /aha <phrase> [+ your hunch]

2026-06-162

drop

OleksandrHavuka/shadowling

Remove words/terms from your vocab list. Comma-separated for several at once. Usage: /drop <word>[, <word2>, ...]

2026-06-162

name	drift
description	Dev: check a target (spec / plan / working diff / code) for architectural drift from the rulebook docs/ARCHITECTURE.md — report qualitative deviations citing rule ids, and triage new ones into docs/Debt.md. Usage: /drift <target>
allowed-tools	Read Grep Glob Bash(git diff) Bash(git status) Edit

Detect architectural drift: does $ARGUMENTS still fit how shadowling is built? The target is a spec/plan path, the working diff (when omitted or changes), or a code path / ..

Behavior:

Every finding cites its R-id + file:line. No matching rule → not a finding — don't free-associate. Bugs are /code-review; reuse/simplify cleanups are /simplify.
Skip the mechanical rules check.sh/tach already enforce (R-MOD, R-DEV-1/2/4) — this gate is the qualitative layer.
Deviations already in docs/Debt.md are known debt: list them as such, never re-raise as new.
For each genuinely new deviation, ask the user whether to record it. On yes, append it under docs/Debt.md ## Open in the file's format: - [ ] R-<id> — <where>: <what deviates> → <target>. Record only what is confirmed.
Also run the rulebook's rule-gap loop ("How this doc is used" → "Self-improvement"): surface rare rule-gap candidates; on approval append the rule to docs/ARCHITECTURE.md, else drop. Never park a candidate.
Never touch production code. Writes are limited to a confirmed docs/Debt.md append (deviation from an existing rule) and, on approval, a new rule in docs/ARCHITECTURE.md. If the target matches the baseline and no gap surfaces, say so and skip triage.