Detect systemic architectural issues across plugins, scripts, and vault organization.
npx skills add https://github.com/sonthanh/brain-os-plugin --skill refactor-sonthanh
Please help me install this Agent Skill. Skill: refactor Source: https://github.com/sonthanh/brain-os-plugin/tree/main/skills/refactor Command: npx skills add https://github.com/sonthanh/brain-os-plugin --skill refactor-sonthanh
System-level reorganization scan across the brain-os plugin + vault scripts + vault organization (and any additional repos the user lists in their personal scope file). Detects shallow modules, cross-skill duplication, unused code, conflicting patterns, and vault organizational drift. Runs weekly via cron (Sunday 02:00 ICT) — produces a report with proposed refactor issues. Use when user wants a system-level refactor scan, architecture review, codebase audit, or says 'reorganize', 'refactor', 'shallow modules', 'is this codebase still in shape', 'improve architecture', audit our architecture', or invokes /refactor. Different from /improve (per-skill, eval-gated) and /vault-lint (mechanical hygiene) — this is structural critique across artifacts.
Run the /refactor skill to perform a weekly system-wide refactor scan and review the generated report.
High-intent search queries and answers about installing and using this skill.
A system-wide codebase refactor scan performs per-file structural analysis across plugins, scripts, and vault organization to detect shallow modules, cross-skill duplication, unused code, and conflicting patterns. It uses five detectors to surface actionable architectural issues in a standardized markdown report.
Architectural drift detection works by running structural critique detectors across vault scripts and organization artifacts on a scheduled cadence. It identifies conflicting patterns and organizational drift, then generates proposed refactor issues and cross-skill consolidation suggestions in a standardized report.
The best way to audit codebase architecture is running a structural refactor scan that applies five per-file detectors to identify shallow modules, unused code, and cross-skill duplication. It supports dry-run modes with checkpointing and honors architecture-exempt frontmatter to skip specific files.
Yes, you can schedule an automated codebase architecture review to run weekly via cron. The scan operates on a weekly cadence, supporting both interactive and cron modes with checkpointing, and outputs a markdown report containing proposed refactor issues at a daily report path.
A structural refactor audit performs system-wide architectural critique across artifacts to find shallow modules and conflicting patterns, while mechanical code hygiene focuses on surface-level linting. The refactor scan generates proposed consolidation issues and can chain downstream for task slicing.
After identifying architectural issues, you should chain the generated refactor report to a task slicing workflow. This converts the proposed refactor issues and cross-skill consolidation suggestions into actionable GitHub issues for downstream execution and action planning.
testdoubleSplit a plan-wide work-items file into per-repo GitHub issues.
kvithayathilBreak PRDs into vertical slice GitHub issues with dependencies and acceptance criteria.
Harmeet10000Configure v2 golangci-lint with recommended linters and nolint directives.
KbediakoDraft and refresh PRD, TECH_SPEC, and ACTION_PLAN artifacts before implementation.
