Menú
Adds a new system directory to the grew configuration so it is created during grew setup.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | add-grew-directory |
| description | Adds a new system directory to the grew configuration so it is created during grew setup. |
When requested to add a new directory to the grew installation structure, follow these steps:
Edit pkg/config/paths.go:
string field to the Paths struct. Document it with its location.FromRoot function. For example: MyNewDir: filepath.Join(root, "my_new_dir").InitDirs(). For example: {Name: "my_new_dir", Path: p.MyNewDir}.Edit pkg/config/paths_test.go:
paths.MyNewDir field to the slice of paths verified in TestInit_CreatesDirectories().Document the structure:
docs/tech.md is updated to reflect the new directory structure.Scaffold a new grew subcommand end-to-end. Use when the user asks to add, create, or scaffold a new CLI command. Reads existing commands for style reference, creates cmd/<name>/ with Command + doc.go, registers in root.go, and updates cmd/README.md.
Add a new diagnostic check to grew doctor. Use when the user wants to add a health check, diagnostic, or validation to the `grew doctor` command. Follows the registration-via-init() pattern so the core flow is never edited directly.
Run a security audit on the current branch's changes. Use when the user asks to audit, security-review, or check for vulnerabilities in pending changes. Spawns the security-auditor agent against the diff.
Run grew's test suite at the appropriate level. Use when the user asks to run tests, check if tests pass, or verify a change didn't break anything. Accepts an optional level argument (unit, integration, smoke, e2e, all) and an optional package path.