Nm Pensive Code Refinement
by @athola
Improves code quality across duplication, efficiency, and architectural fit
clawhub install nm-pensive-code-refinementπ About This Skill
name: code-refinement description: | Improve code quality: duplication, efficiency, clean code, architectural fit, and error handling version: 1.9.4 triggers: - refactoring - clean-code - algorithms - duplication - anti-slop - craft metadata: {"openclaw": {"homepage": "https://github.com/athola/claude-night-market/tree/master/plugins/pensive", "emoji": "\ud83e\udd9e", "requires": {"config": ["night-market.pensive:shared", "night-market.pensive:safety-critical-patterns", "night-market.imbue:proof-of-work"]}}} source: claude-night-market source_plugin: pensive
> Night Market Skill β ported from claude-night-market/pensive. For the full experience with agents, hooks, and commands, install the Claude Code plugin.
Table of Contents
Code Refinement Workflow
Analyze and improve living code quality across six dimensions.
Quick Start
/refine-code
/refine-code --level 2 --focus duplication
/refine-code --level 3 --report refinement-plan.md
When To Use
When NOT To Use
Analysis Dimensions
| # | Dimension | Module | What It Catches |
|---|-----------|--------|----------------|
| 1 | Duplication & Redundancy | duplication-analysis | Near-identical blocks, similar functions, copy-paste |
| 2 | Algorithmic Efficiency | algorithm-efficiency | O(n^2) where O(n) works, unnecessary iterations |
| 3 | Clean Code Violations | clean-code-checks | Long methods, deep nesting, poor naming, magic values |
| 4 | Architectural Fit | architectural-fit | Paradigm mismatches, coupling violations, leaky abstractions |
| 5 | Anti-Slop Patterns | clean-code-checks | Premature abstraction, enterprise cosplay, hollow patterns |
| 6 | Error Handling | clean-code-checks | Bare excepts, swallowed errors, happy-path-only |
Progressive Loading
Load modules based on refinement focus:
modules/duplication-analysis.md (~400 tokens): Duplication detection and consolidationmodules/algorithm-efficiency.md (~400 tokens): Complexity analysis and optimizationmodules/clean-code-checks.md (~450 tokens): Clean code, anti-slop, error handlingmodules/architectural-fit.md (~400 tokens): Paradigm alignment and couplingLoad all for comprehensive refinement. For focused work, load only relevant modules.
Required TodoWrite Items
1. refine:context-established β Scope, language, framework detection
2. refine:scan-complete β Findings across all dimensions
3. refine:prioritized β Findings ranked by impact and effort
4. refine:plan-generated β Concrete refactoring plan with before/after
5. refine:evidence-captured β Evidence appendix per imbue:proof-of-work
Workflow
Step 1: Establish Context (refine:context-established)
Detect project characteristics:
# Language detection
find . -not -path "*/.venv/*" -not -path "*/__pycache__/*" \
-not -path "*/node_modules/*" -not -path "*/.git/*" \
\( -name "*.py" -o -name "*.ts" -o -name "*.rs" -o -name "*.go" \) \
| head -20Framework detection
ls package.json pyproject.toml Cargo.toml go.mod 2>/dev/nullSize assessment
find . -not -path "*/.venv/*" -not -path "*/__pycache__/*" \
-not -path "*/node_modules/*" -not -path "*/.git/*" \
\( -name "*.py" -o -name "*.ts" -o -name "*.rs" \) \
| xargs wc -l 2>/dev/null | tail -1
Step 2: Dimensional Scan (refine:scan-complete)
Load relevant modules and execute analysis per tier level.
Step 3: Prioritize (refine:prioritized)
Rank findings by:
Priority = HIGH impact + SMALL effort + LOW risk first.
Step 4: Generate Plan (refine:plan-generated)
For each finding, produce:
Step 5: Evidence Capture (refine:evidence-captured)
Document with imbue:proof-of-work (if available):
[E1], [E2] references for each findingFallback: If imbue is not installed, capture evidence inline in the report using the same [E1] reference format without TodoWrite integration.
Tiered Analysis
| Tier | Time | Scope | |------|------|-------| | 1: Quick (default) | 2-5 min | Complexity hotspots, obvious duplication, naming, magic values | | 2: Targeted | 10-20 min | Algorithm analysis, full duplication scan, architectural alignment | | 3: Deep | 30-60 min | All above + cross-module coupling, paradigm fitness, comprehensive plan |
Cross-Plugin Dependencies
| Dependency | Required? | Fallback |
|------------|-----------|----------|
| pensive:shared | Yes | Core review patterns |
| imbue:proof-of-work | Optional | Inline evidence in report |
| conserve:code-quality-principles | Optional | Built-in KISS/YAGNI/SOLID checks |
| archetypes:architecture-paradigms | Optional | Principle-based checks only (no paradigm detection) |
Supporting Modules
When optional plugins are not installed, the skill degrades gracefully:
imbue: Evidence captured inline, no TodoWrite proof-of-workconserve: Uses built-in clean code checks (subset)archetypes: Skips paradigm-specific alignment, uses coupling/cohesion principles onlyβ‘ When to Use
π‘ Examples
/refine-code
/refine-code --level 2 --focus duplication
/refine-code --level 3 --report refinement-plan.md