tvproductions
@tvproductions Organization
Public Skills
gzs-project-setup
by tvproductions
Initialize or inspect a repository's GovZero skills profile. Use on first GovZero skill use in a project, when choosing lite or heavy, or when promoting an existing lite project to heavy; stop if the project uses gzkit.
gzs-pythonic-pattern-apply
by tvproductions
Apply one authorized Pythonic design-pattern refactor while proving behavior and relevant boundaries remain intact. Use after a concrete candidate and target are selected; do not activate for general feature work or an unapproved codebase-wide rewrite.
gzs-router
by tvproductions
Orient users to the GovZero portable skill catalog. Use when they need the right skill or sequence, ask how to discover, invoke, install, or update GovZero skills, or need help diagnosing skill availability or invocation behavior.
gzs-update-dependencies
by tvproductions
Reconcile an adopted project profile and refresh project-managed dependencies, runtime pins, package-manager tooling, lockfiles, and development tools to current supported releases, then run full verification. Use when the user asks to update all dependencies and tools, upgrade packages, refresh lockfiles, bump runtimes, or bring a project's toolchain current.
gzs-pythonic-pattern-detect
by tvproductions
Review Python code for concrete design-pattern shapes that could be simpler with Python constructs. Use for a requested Pythonic pattern review or to triage suspected Java-style class scaffolding; do not use as a general lint or architecture audit.
gzs-hexagonal-architecture-audit
by tvproductions
Analyze greenfield designs and brownfield implementations against right-sized hexagonal architecture, then coach boundary-preserving design or refactoring. Use for explicit hexagonal or ports-and-adapters audits, architecture work involving dependency direction or cross-project interoperability, or projects that declare these guardrails; do not use for ordinary code review, generic SOLID questions, or structurally simple projects.
gzs-dependency-risk-audit
by tvproductions
Assess a project's direct and transitive dependency risks using manifests, lockfiles, authoritative advisories, compatibility constraints, maintenance signals, licenses, provenance, and actual repository usage. Use for dependency-risk, supply-chain, vulnerability, abandonment, or license audits; not for automatically upgrading packages or performing a general security review.
gzs-session-handoff
by tvproductions
Create or resume a durable engineering-session handoff that preserves state, decisions, evidence, and next actions without duplicating existing artifacts. Use when the user explicitly asks to hand off, checkpoint, resume, or preserve work for another session or agent.
gzs-root-cause-debugging
by tvproductions
Diagnose technical failures through reproducible evidence and falsifiable hypotheses. Use when diagnosing or fixing a bug, failing test, regression, intermittent failure, or unexplained performance problem whose cause is not yet demonstrated; yield to any active project-owned incident, execution, or governance workflow.
gzs-repository-hygiene
by tvproductions
Audit and, when requested, repair repository hygiene across workspace state, generated artifacts, packaging boundaries, lockfiles, caches, and control-surface drift. Use for maintenance, cleanup, tidy, repository-health, or generated-artifact verification requests; use project-owned hygiene commands when present.
gzs-change-review
by tvproductions
Review a bounded implementation change for defects, regressions, unsafe assumptions, and maintainability risks, then report prioritized evidence-backed findings. Use for code review, diff review, pre-merge review, or independent assessment of a completed change; not for running only automated checks, auditing broad technical debt, or implementing fixes.
gzs-intent-audit
by tvproductions
Trace declared intent to observed shipped behavior and classify gaps as corrections rather than new design. Use when a capability exists but may not fulfill its specification, during a pre-release integrity review, or when checking whether completed work actually delivered what was decided.
gzs-plan-audit
by tvproductions
Audit alignment among declared intent, scoped requirements, and an execution plan before implementation begins. Use when reviewing a plan, leaving plan mode, starting a planned change, or checking for missing requirements, forbidden paths, scope creep, or inadequate verification.
gzs-quality-gate
by tvproductions
Run and evidence the repository's complete required quality gate for the current change. Use for pre-handoff, pre-merge, pre-release, or explicit full-verification requests; use the project's declared commands rather than assuming a language or toolchain.
gzs-tech-debt-review
by tvproductions
Survey scoped technical debt using the repository's existing analyzers and render a prioritized, evidence-grounded report without implementing fixes. Use for technical-debt reviews of changed files, a component, a work item, or the whole repository.
gzs-test-driven-change
by tvproductions
Implement one authorized behavior change through a tight red-green-refactor loop with an assertion-level failing test as the negative control. Use when the user explicitly requests test-driven development, test-first work, or red-green-refactor; do not activate merely because an ordinary implementation should include tests.
gzs-agent-context-diet
by tvproductions
Reduce always-loaded agent instruction weight while preserving every binding invariant through progressive disclosure and precise context pointers. Use when AGENTS.md, CLAUDE.md, repository rules, or skill descriptions have accumulated duplicated rationale or exceed an enforced context budget.
gzs-git-sync
by tvproductions
Create and publish a guarded Git save point after reviewing scope and passing the repository's own quality gates. Use only when the user explicitly asks to git sync, commit and push, publish the current work, or create a remote save point.
gzs-cross-platform-python
by tvproductions
Review or implement Python filesystem, text, subprocess, temporary-resource, and test behavior for Windows, macOS, and Linux portability. Use when Python code handles paths, files, encodings, processes, cleanup, platform branches, or failures seen on only one operating system.