skills.rest
pnils08
pnils08COMMUNITY
Explore all skills by this author →
GitHub

tech-debt-audit

Identifies code-health issues in phase*/ and utilities/ JavaScript sources, including Math.random() usage and dead code, with severity and file references.

1|Updated Jan 15, 2026
Search Tags:#audit#determinism#dead-code#code-health#ctx-fields#phase-scanning#googles-apps-script
One-click install
npx skills add https://github.com/pnils08/GodWorld --skill tech-debt-audit-pnils08
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt-audit
Source: https://github.com/pnils08/GodWorld/tree/main/.claude/skills/tech-debt-audit
Command: npx skills add https://github.com/pnils08/GodWorld --skill tech-debt-audit-pnils08

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated scans identify code-health issues across all engine files to reduce risk from determinism violations, orphaned ctx fields, dead code, and structural drift.

Core Features & Use Cases

  • Detects Math.random() usage without proper RNG handling across phase*/ and utilities/ files.
  • Flags direct Sheet API writes outside phase 10 boundaries and tracks documented exceptions.
  • Finds orphaned ctx fields and dead code, and surfaces sheet-header misalignment issues.
  • Provides a prioritized inventory with file:line references and severity for remediation.

Quick Start

Run the tech-debt-audit skill after major engine changes or every few sessions to generate a prioritized issue inventory.

Frequently Asked Questions about tech-debt-audit

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

FAQPage Schema
How do I detect Math.random() determinism violations in Google Apps Script?▼

Detect determinism violations by scanning phase*/ and utilities/ JavaScript sources for Math.random() usage without proper RNG handling. The audit flags these violations with severity levels and file references.

What is the best way to find dead code and orphaned ctx fields in engine files?▼

Find dead code and orphaned ctx fields by running an automated inventory scan across all engine files. The audit identifies unused fields and dead code, reporting each issue with file:line references and severity.

How do I check for direct Sheet API writes outside of specific phase boundaries?▼

Check for direct Sheet API writes outside phase 10 by applying a scan to JavaScript sources that flags boundary violations and tracks documented exceptions, providing a prioritized inventory of findings.

When should I run a code health audit on my engine files?▼

Run a code health audit after major engine changes or at regular intervals every few sessions. This periodic scanning identifies structural drift, sheet-header misalignment, and determinism issues early.

Can I audit sheet-header misalignment issues in Google Apps Script projects?▼

Yes, you can audit sheet-header misalignment by scanning engine files. The audit surfaces structural drift between expected headers and actual sheet structure, reporting findings with severity and file references.

Related Skills

Explore More Software Engineering Skills→
m13vm13v
312

gws-apps-script-push

Upload local script files to a specified Google Apps Script project.

Community
Basic
pnils08pnils08
1

pre-mortem

Scan engine phases for silent failures before a cycle run.

Community
Advanced
fishyerfishyer
1

gws-script

Automate project management and process monitoring for Google Apps Script projects.

Community
Intermediate
DanielKerridgeDanielKerridge
56

code-review

Audit codebases across seven passes and output severity-scoped reports.

Community
Advanced