skills.rest
RhyTsui
RhyTsuiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pmos-historical-code-review

Convert legacy hotspots into categorized remediation backlog recommendations.

Updated May 9, 2026
Search Tags:#drift prevention#remediation backlog#architecture debt#risk categorization#historical code review#legacy hotspots#governed findings
One-click install
npx skills add https://github.com/RhyTsui/PMOS --skill pmos-historical-code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pmos-historical-code-review
Source: https://github.com/RhyTsui/PMOS/tree/main/skills/pmos-historical-code-review
Command: npx skills add https://github.com/RhyTsui/PMOS --skill pmos-historical-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents long-term legacy fragility from quietly disappearing when current delivery work ends, by turning historical hotspot concerns into explicit, trackable remediation follow-ups.

Core Features & Use Cases

  • Hotspot-first historical audit: Focuses review on specific legacy hotspots instead of doing whole-repo brute-force scanning.
  • Debt governance lane: Segregates historical issues into immediate delivery risk versus non-blocking debt and remediation candidates.
  • Remediation queue output contract: Produces clear backlog recommendations so historical problems become actionable work, not buried notes.
  • Escalation rule for blockers: Escalates only when historical risk becomes a real current delivery blocker.

Quick Start

Use the pmos-historical-code-review skill to review the legacy hotspot that keeps causing repeated drift and generate a remediation queue with immediate risks and backlog follow-ups.

Frequently Asked Questions about pmos-historical-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn legacy code hotspots into trackable remediation backlog items?▼

Historical code review converts repeated code drift and legacy fragility into governed remediation work by producing categorized findings that separate immediate delivery risks from non-blocking architecture debt backlog items.

What is the best way to categorize architecture debt discovered during a legacy code review?▼

The best way to categorize discovered architecture debt is using a governance lane that segregates historical issues into immediate delivery risks versus non-blocking debt and remediation candidates.

How do I prevent code drift in legacy hotspots from disappearing after current delivery work ends?▼

You prevent code drift from disappearing by converting historical hotspot risks into explicit remediation queue outputs with backlog follow-ups, ensuring historical problems remain governed and trackable across iterations.

Does this historical code review approach scan the entire repository for architecture debt?▼

No, this approach does not brute-force scan the entire repository. It performs a hotspot-first historical audit that focuses review specifically on identified legacy hotspots causing repeated drift.

When should I escalate a historical risk found during a legacy code review?▼

You should escalate a historical risk only when it becomes a real current delivery blocker. Non-blocking architecture debt is routed to the remediation queue as a backlog follow-up instead.

Related Skills

Explore More Software Engineering Skills→
thejefflarsonthejefflarson
20

hotspots

Identify security hotspots in a codebase and output a prioritized report.

Community
Advanced
AugustEmnaAugustEmna

follow-up-tasks

Convert current work into categorized follow-up tasks via proposeFollowUpTasks.

Community
Intermediate
coolbeevipcoolbeevip
8

team-tech-debt-analyze

Analyze technical debt via read-only inspection and evidence-based reports.

Community
Advanced
SkobynSkobyn

hunt-brute-force

Detect login brute force, OTP/2FA brute force, and credential stuffing vulnerabilities.

Community
Advanced