Skip to content
cccskills
FreePublished on GitHub

dygo-thermonuclear-review

Run an explicitly requested, unusually strict dygo maintainability audit that seeks structural simplification, removes accidental complexity, and challenges weak abstractions without changing behavior.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (2)

  • SKILL.md1.8 KB
  • agents/openai.yaml43 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

dygo Thermonuclear Review

Use this skill only when the user asks for a thermonuclear, severe, exhaustive, or especially harsh code-quality review.

Standard

Search for a structural move that deletes concepts, branches, modes, wrappers, duplication, or special cases. Do not stop at local style comments.

Challenge:

  • framework capability hidden in a private Core-only path;
  • Business App logic inside reusable framework packages;
  • duplicated metadata decoding, naming, permission, query, or API contracts;
  • files and components that became too large to reason about;
  • scattered conditionals that indicate a missing model or policy;
  • pass-through abstractions and generic mechanisms that hide simple data flow;
  • optionality, casts, maps, or fallbacks that conceal an invariant;
  • non-atomic related updates and avoidable sequential orchestration;
  • one-off Studio patterns outside the design system;
  • public SDK surface that has not earned a compatibility promise.

Boundaries

  • Keep an audit read-only unless implementation is authorized. Refactoring must preserve behavior; change behavior only within an authorized feature or fix, and explain the difference.
  • For parallel reviews, assign distinct subsystems or concerns and require code evidence. Reconcile overlapping findings before applying changes.
  • Do not reward novelty. Prefer direct and boring structure.
  • Support every finding with concrete code evidence and maintenance impact.
  • Distinguish a defect from an ambitious redesign opportunity.
  • Do not require broad rewrites when a smaller structural correction removes the same complexity.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design, implement, or review dygo roles, Entity access metadata, Permissions, and permission-aware Business App behavior. Use when access to Records or business actions is central to the task.

The English summary is being prepared. Showing the original description.

hapyco/dygo16Updated Oct 18, 2026

Design, implement, or review dygo HTTP APIs and public App SDK contracts. Use for Record APIs, metadata and boot endpoints, query behavior, response envelopes, compatibility, and public Go interfaces.

The English summary is being prepared. Showing the original description.

hapyco/dygo16Updated Oct 18, 2026

Diagnose a dygo Business App that does not validate, boot, route, render, authorize, migrate, or execute background work correctly. Use for evidence-first investigation rather than feature implementation.

The English summary is being prepared. Showing the original description.

hapyco/dygo16Updated Oct 18, 2026

Build or extend a dygo Business App using the supported project layout, generators, metadata, SDK, and validation workflow. Use for general app work that is not primarily Entity modeling, access, hooks, Jobs, fixtures, or patches.

The English summary is being prepared. Showing the original description.

hapyco/dygo16Updated Oct 18, 2026

Review a dygo Business App for framework conventions, model quality, access control, SDK boundaries, observability, and safe lifecycle behavior. Use for App audits and pre-merge reviews, not ordinary implementation.

The English summary is being prepared. Showing the original description.

hapyco/dygo16Updated Oct 18, 2026

Design, implement, or review the dygo framework CLI in Go with Cobra. Use for commands, flags, help, prompts, plans, output contracts, completion, and project-aware CLI behavior. Do not use for operating a deployed business through the reserved dygo-cli operator skill.

The English summary is being prepared. Showing the original description.

hapyco/dygo16Updated Oct 18, 2026

See all skills by hapyco

Report a problem with this skill