Skip to content
cccskills
FreePublished on GitHub

dygo-cli-development

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.

See how to install

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

dygo CLI Development

Develop the CLI implementation. This skill does not perform business operations on a deployment.

Structure

  • Keep cmd/dygo/main.go small and call the CLI runner.
  • Put command implementation under internal/cli.
  • Construct the root with injected context, stdin, stdout, and stderr.
  • Keep SilenceUsage and SilenceErrors enabled.
  • Use RunE and explicit Args validation.
  • Use project-root discovery for commands that read project files.
  • Keep command logic small. Put reusable behavior in the owning framework package.

Command Contract

  • Follow the resource-first command surface in docs/cli.md.
  • Send stable normal output to stdout. Send prompts, warnings, and diagnostics to stderr.
  • Keep output plain, concise, and usable by people and agents.
  • Redact secrets and credentials.
  • For material writes, show the target and plan before the prompt.
  • Support --dry-run when planning is meaningful and --yes when non-interactive use is safe.
  • Make destructive commands explicit. Never hide destructive work inside an additive command.
  • Do not add Viper until dygo needs shared flag, environment, file, and default precedence.
  • Keep completion fast, local, and read-only.

Check

Use focused internal/cli tests and inspect help for changed command trees. Test injected streams, invalid arguments, nested project discovery, and safety behavior when relevant.

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

Improve or review ordinary dygo code changes for simplicity, focused scope, canonical ownership, clear boundaries, and verifiable behavior. Use for normal implementation and refactoring quality; use dygo-thermonuclear-review only for an explicitly severe audit.

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