Run a code-level convention audit across the codebase. Use when checking for naming drift, magic strings, dead exports, and doc alignment before a release or after a heavy development session.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Run a code-level convention audit across the codebase. Use when checking for naming drift, magic strings, dead exports, and doc alignment before a release or after a heavy development session.
Run a code-level consolidation pass on the ctx codebase. This
complements ctx drift (which checks context-level drift) by
checking source code against project conventions.
Before Consolidating
Check the ratio: have there been 3+ sessions since the
last consolidation? If not, it may be too early
Clean working tree: git status should show no
uncommitted changes; consolidation touches many files and
you need a clean diff baseline
Run tests first: make audit should pass before you
start; do not consolidate on top of a broken build
When to Use
After 3+ rapid sessions (the 3:1 ratio)
Before tagging a release
When a session touched many files
When you suspect convention drift
When NOT to Use
Mid-feature when code is intentionally incomplete
Immediately after the last consolidation with no new work
in between
When the user is focused on shipping and explicitly defers
cleanup
Usage Examples
/_ctx-audit
/_ctx-audit (before v0.3.0 release)
/_ctx-audit (after the YOLO sprint this week)
Checks
Before running checks mechanically, reason through which areas
are most likely to have drifted based on recent changes. This
focuses attention where it matters most.
Run each check in order. Report findings per check, then summarize.
1. Predicate Naming
Convention: no Is/Has/Can prefixes on exported bool-returning methods.
rg '^\s*func\s+\([^)]+\)\s+(Is|Has|Can)[A-Z]\w*\(' --type go -l
Mark these as accepted exceptions:
IsUser(), IsAssistant() on Message: dropping Is makes
these look like getters (msg.User() reads as "get user?").
The prefix earns its keep.
Fix: Rename to drop the prefix. IsPending() → Pending().
Flag any NEW Is/Has/Can methods not listed as exceptions above.
2. Magic Strings
Convention: literals used in 3+ files need a constant.
# Find repeated string literals across files
rg '"[A-Z][A-Z_]+\.md"' --type go -c | sort -t: -k2 -rn
rg '"\.context/' --type go -c | sort -t: -k2 -rn
Check internal/config/ for existing constants. If a literal is already
defined there but not used everywhere, that's a drift.
Fix: Replace literal with the constant from internal/config/.
3. Hardcoded Permissions
Convention: file permissions should use named constants, not literals.
rg '0[67][0-7][0-5]' --type go -l
Fix: Define constants in internal/config/ if missing, then reference them.
4. File Size
Convention: source files > 300 LOC should be evaluated for splitting.
Files over 300 LOC: check if they mix public API with private helpers
(convention says split them).
5. TODO/FIXME in Source
Constitution: no TODO comments in main branch (move to TASKS.md).
rg 'TODO|FIXME|HACK|XXX' --type go -n
Fix: Move the item to .context/TASKS.md, delete the comment.
6. Path Construction
Constitution: path construction uses stdlib, no string concatenation.
rg '"\.\./|"/"|"/" \+|+ "/"' --type go -l
Fix: Replace with filepath.Join().
7. Line Width
Highly encouraged: keep lines to ~80 characters. This is not a hard limit —
some lines (long string literals, struct tags, URLs) will exceed it and that's
fine. But drift happens quietly, especially in test code where long assertion
messages and deeply nested structs push lines wide without anyone noticing.
# Lines exceeding 100 chars (flag the worst offenders, not every 81-char line)
rg '.{101,}' --type go -c | sort -t: -k2 -rn | head -20
Fix: Break long lines at natural points: function arguments,
struct fields, chained calls. For test code, extract repeated
long values into local variables or constants.
8. Duplicate Code Blocks
Drift pattern: copy-paste blocks accumulate when the agent is focused on
getting the task done rather than keeping the code in shape. This is
especially common in test files but also appears in non-test code.
In test code, some duplication is acceptable; test readability matters.
But when the same setup/assertion block appears 3+ times, consider a test
helper (testutil or unexported helpers in _test.go).
In non-test code, apply the Consolidation Decision Matrix below.
# Heuristic: find functions with very similar signatures in the same package# Manual review is more effective here; look for:# - Identical error-handling blocks# - Repeated struct construction# - Copy-paste command setup patterns
Fix (tests): Extract a helper function in the same _test.go file.
Use t.Helper() so failure messages point to the caller.
Fix (non-test): Extract shared logic into a package-level unexported
function, or into a shared internal package if it spans packages.
9. Architecture Diagram Drift
After structural changes (new packages, moved files, changed
dependencies), verify .context/ARCHITECTURE.md diagrams match
actual code:
# Compare packages listed in ARCHITECTURE.md to actual packagesls internal/
# Compare dependency graph claims to actual imports
grep -r '"github.com/ActiveMemory/ctx/internal/' internal/ | \
sed 's|.*ctx/internal/|internal/|' | sort -u
Fix: Update the component map table, dependency graph, and file
layout sections in .context/ARCHITECTURE.md. Run ctx drift to
verify no dead path references remain.
10. Dead Exports
Check for exported functions/types with no callers outside their package.
# Quick heuristic: exported func defined but only used in its own package
Use go vet and golangci-lint run --enable=unused for a more thorough check.
11. Package Documentation Drift
Convention: packages with a doc.go must stay accurate in two ways:
a) File Organization listing — must list every .go file in the
package (excluding _test.go). Missing or extra entries mean files
were added/removed without updating the doc.
make lint-docs
b) Package description — the opening paragraph describes what the
package does. When behavior changes (new subcommands, new
responsibilities, renamed concepts), the description drifts.
Review each doc.go manually: does the description still match what
the package actually does today? Check exported symbols, command
Use/Short/Long strings, and the file organization listing for
clues that the scope expanded or shifted.
Fix (a): Add missing files, remove stale entries.
Fix (b): Rewrite the description to match current behavior.
12. Dead Doc Links
Documentation links drift when pages are renamed, moved, or deleted.
Run /ctx-link-check (if installed) to scan all docs/ markdown files for:
Internal links pointing to files that don't exist
External links that return errors (reported as warnings, not failures)
Image references to missing files
Internal broken links count as findings to fix. External failures are
informational — network partitions happen.
13. ctxrc Schema Drift
Three sources of truth define .ctxrc options and must stay in sync:
internal/rc/types.go — the CtxRC struct (yaml tags are the keys)
.ctxrc — the sample config in the project root
docs/configuration.md — the "Full Reference" yaml block and the
"Option Reference" table
Drift patterns:
A new field is added to the struct but not to the sample or docs
A field is removed from the struct but lingers in the sample or docs
A yaml tag is renamed but the sample/docs still use the old key
Default values diverge between the struct defaults (rc.go:Default())
and the commented values in the sample / docs table
# Extract yaml tags from the struct
rg 'yaml:"(\w+)"' internal/rc/types.go -o --replace '$1'# Extract commented keys from the sample .ctxrc (top-level scalars)
rg '^#?\s*(\w+):' .ctxrc -o --replace '$1' | grep -v '^#'# Extract keys from the docs Full Reference block
rg '^#?\s*(\w+):' docs/configuration.md -o --replace '$1' | grep -v '^#'
Fix: Add missing keys to the sample and docs, or remove stale ones.
Ensure default values in the sample comments match rc.Default() and the
docs Option Reference table.
14. Makefile Target Drift
Skills and docs reference Makefile targets (e.g., make audit, make lint-docs,
make smoke). Targets get renamed or removed without updating references.
# Extract all .PHONY targets from the Makefile
rg '\.PHONY:' Makefile | tr' ''\n' | grep -v '\.PHONY' | sort -u
# Find Makefile target references in skills and docs
rg 'make \w+' .claude/skills/ docs/ --type md -o | sort -u
Compare the two lists. Any referenced target that doesn't exist in the
Makefile is a finding.
Fix: Update the reference to the current target name, or restore
the target if it was removed accidentally.
15. Skill Metadata Drift
Skill directories under .claude/skills/ and skill entries in
internal/assets/permissions/allow.txt must stay aligned.
Skills get renamed (e.g., ctx-borrow → absorb) but stale references
linger in permission lists, docs, or other skills.
# List skill directoriesls .claude/skills/
# List ctx-plugin skill directoriesls .claude/ctx-skills/ 2>/dev/null
# Extract Skill() entries from allow.txt
grep '^Skill(' internal/assets/permissions/allow.txt | sort -u
# Find cross-references to skill names in other skills
rg '/\w[-\w]+' .claude/skills/ --type md -o | sort -u
Check:
Every skill directory has a matching Skill() permission entry (or is
intentionally unpermissioned)
No Skill() entry references a skill that no longer exists
TestDefaultPermissions in embed_test.go catches drift automatically
Cross-references between skills use current names
Fix: Update stale names in permission lists and cross-references.
16. Config Constant Drift
internal/config/ defines constants (DirContext, FileReadOrder,
DefaultTokenBudget, etc.) that docs and the sample .ctxrc cite as
defaults. When constants change, docs lag behind.
# Extract key constants and their values
rg 'const|var' internal/config/file.go internal/config/dir.go \
internal/rc/types.go internal/rc/rc.go --type go -A1
# Check docs claim the same defaults
rg 'default|Default' docs/configuration.md -n
Cross-check:
FileReadOrder entries match the priority_order list in sample
.ctxrc and the docs "Default priority order" section
DefaultTokenBudget, DefaultArchiveAfterDays, etc. in rc.go
match the commented values in .ctxrc and docs Option Reference table
Fix: Align the docs/sample values to match the code constants.
17. CLI Subcommand Drift
docs/cli-reference.md documents commands and flags. When commands are
added, renamed, or removed, the docs drift.
Also check that global flags documented in docs/configuration.md
match the flags actually registered in internal/bootstrap/cmd.go.
Fix: Add missing commands/flags to the docs, or remove stale entries.
18. YAML Content Drift
Structural linkage (keys exist in both YAML and code) is tested
by TestDescKeyYAMLLinkage, TestExamplesYAMLLinkage, and
TestRegistryYAMLLinkage. Content-level drift is tested by
TestFlagYAMLMatchesConstants and TestCommandYAMLMatchesDescKeys.
Beyond what tests catch, check semantically:
Do flag descriptions in flags.yaml still accurately describe
what the flag does? (Tests verify the name; humans verify prose.)
Do command descriptions in commands.yaml match current behavior?
(A command that gained flags or changed semantics may have stale
Short/Long text.)
Do examples in examples.yaml still work? Run a sample:
# Pick 3-5 examples and run them
grep -A2 'short:' internal/assets/commands/examples.yaml | \
grep '^\s*ctx ' | head -5
Fix: Update stale descriptions to match current behavior.
Descriptions are user-facing --help text — accuracy matters.
Consolidation Decision Matrix
Use this to prioritize what to fix:
Similarity
Instances
Action
Exact duplicate
2+
Consolidate immediately
Same pattern, different args
3+
Extract with parameters
Similar shape
5+
Consider abstraction
< 3 instances
Any
Leave it; duplication is cheaper than wrong abstraction
Safe Migration Pattern
When consolidating would change public API:
Create new function alongside old
Deprecate old with // Deprecated: godoc comment
Migrate callers incrementally
Delete old function when no callers remain
Avoid bulk-renaming across packages in a single commit — it makes
bisecting regressions and reviewing diffs significantly harder.
