unic-senior-review

Étoiles14

Forks1

Mis à jour9 avril 2026 à 04:30

Use when the user wants a deep maintainability or refactoring review of the unic codebase, including file-size analysis, Go idioms, and concrete refactoring priorities. Do not use for normal bug reviews or feature implementation.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

DevopsArtFactory

DevopsArtFactory/unic

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	unic-senior-review
description	Use when the user wants a deep maintainability or refactoring review of the unic codebase, including file-size analysis, Go idioms, and concrete refactoring priorities. Do not use for normal bug reviews or feature implementation.

Conduct a senior-engineer style review of unic focused on code quality, maintainability, and refactoring opportunities.

Workflow

Start with a line-count inventory.

Run find internal/ cmd/ -name '*.go' | xargs wc -l | sort -rn.
Run find internal/ cmd/ -name '*_test.go' | xargs wc -l | sort -rn.
When GitHub access is available, run gh issue list --state open --limit 50 so you can distinguish already-tracked work from net-new findings.
Produce a table with File, Lines, and Status.
Flag files over 300 lines as [LONG] and over 500 lines as [CRITICAL].

Review the code against these categories.

file size and function length
naming and readability
SOLID, abstraction, and DRY pressure
error handling and edge cases
Go-specific idioms such as context flow, error wrapping, goroutine cleanup, and defer usage

Keep the review actionable.

Lead with concrete findings.
Include file references.
Give a specific refactoring suggestion for every finding.
Call out when a finding already appears to be tracked by an open GitHub issue.
Avoid style-only feedback unless it hides a real maintenance risk.
Do not nitpick test-file length unless there is a real quality issue.

End with a report.

Executive summary
LoC breakdown table
Findings ordered by severity
Top 5 refactoring priorities
Positive patterns worth preserving

Optional persistence

If the user wants the report saved, prefer .agents/reports/senior-review-YYYY-MM-DD.md. You may read legacy reports from .claude/reports/ for context when helpful.

Plus depuis ce dépôt

même dépôt

unic-ux-review

DevopsArtFactory/unic

Use when the user asks to run unic locally, capture TUI screenshots, review the Bubble Tea UX, suggest UX improvements, or optionally implement scoped UX polish in the unic repository. This skill is for terminal UI review and safe UX iteration, not for unrelated feature work, dependency updates, PR shipping, or non-UX code review.

2026-06-1814

unic-update-dependencies

DevopsArtFactory/unic

Use when the user asks to update, bump, refresh, audit, or modernize dependencies, libraries, Go modules, the Go language version, or Go toolchain support in the unic repository. Use for dependency maintenance PRs, safe patch/minor Go module updates, Go version bumps, vulnerability-driven dependency updates, or CI/doc updates tied to dependency or Go version changes. Do not use for unrelated feature work, docs-only edits, or CI refactors unless they are required by the dependency/toolchain update.

2026-06-1814

unic-implement-feature

DevopsArtFactory/unic

Use when the user asks to implement a feature, milestone item, or GitHub issue in the unic repository, especially new AWS service work. Do not use for pure refactors, docs-only updates, PR shipping, or issue triage.

2026-04-2614

unic-refactor-review

DevopsArtFactory/unic

Use when the user asks to implement refactors from a prior unic senior review report. Do not use for new features or behavior changes.

2026-04-2614

unic-ship-pr

DevopsArtFactory/unic

Use when the user explicitly asks to stage, commit, push, and open a pull request for unic. Do not use for general coding work or docs-only sync unless the user is asking to ship the current branch.

2026-04-2614

unic-create-issues

DevopsArtFactory/unic

Use when the user asks to create GitHub issues from planned but unimplemented unic work in PLAN.md. Do not use for editing existing issues or for implementation.

2026-04-0914

name	unic-senior-review
description	Use when the user wants a deep maintainability or refactoring review of the unic codebase, including file-size analysis, Go idioms, and concrete refactoring priorities. Do not use for normal bug reviews or feature implementation.

Conduct a senior-engineer style review of unic focused on code quality, maintainability, and refactoring opportunities.

Workflow

Start with a line-count inventory.

Run find internal/ cmd/ -name '*.go' | xargs wc -l | sort -rn.
Run find internal/ cmd/ -name '*_test.go' | xargs wc -l | sort -rn.
When GitHub access is available, run gh issue list --state open --limit 50 so you can distinguish already-tracked work from net-new findings.
Produce a table with File, Lines, and Status.
Flag files over 300 lines as [LONG] and over 500 lines as [CRITICAL].

Review the code against these categories.

file size and function length
naming and readability
SOLID, abstraction, and DRY pressure
error handling and edge cases
Go-specific idioms such as context flow, error wrapping, goroutine cleanup, and defer usage

Keep the review actionable.

Lead with concrete findings.
Include file references.
Give a specific refactoring suggestion for every finding.
Call out when a finding already appears to be tracked by an open GitHub issue.
Avoid style-only feedback unless it hides a real maintenance risk.
Do not nitpick test-file length unless there is a real quality issue.

End with a report.

Executive summary
LoC breakdown table
Findings ordered by severity
Top 5 refactoring priorities
Positive patterns worth preserving

Optional persistence

If the user wants the report saved, prefer .agents/reports/senior-review-YYYY-MM-DD.md. You may read legacy reports from .claude/reports/ for context when helpful.