oosh-module

Estrelas33

Forks0

Atualizado4 de abril de 2026 às 22:07

Create a new module for an oosh CLI. Use /oosh-module <cli> <module> to generate an annotated .sh file in the CLI's modules directory. Trigger when the user wants to add a command, module, or feature to an existing oosh CLI.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

bruno-de-queiroz

bruno-de-queiroz/oosh

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	oosh-module
description	Create a new module for an oosh CLI. Use /oosh-module <cli> <module> to generate an annotated .sh file in the CLI's modules directory. Trigger when the user wants to add a command, module, or feature to an existing oosh CLI.

/oosh-module — Create a new module

Create a new module file in the CLI's modules directory.

Steps

Determine the modules path: ~/.<cli>/modules/ (default) — if the CLI was generated to a custom path, ask the user
Ask what commands and flags the module should expose
Write <module>.sh following the conventions below
Run oosh lint <cli> <module> to validate the new module

Conventions

Read references/annotations.md in this skill directory for the full annotation reference and module template.

Key rules:

File starts with #!/bin/bash and #@module <Name> - <description>
Import the engine: . ${MODULES_DIR}/../oo.sh
Variable names: UPPER_SNAKE_CASE, prefixed with module name (e.g., DEPLOY_ENV in deploy.sh)
End with main $0 "$@"
No sed, awk, grep in hot paths — bash builtins only
Bash 3.2 compatible

Mais deste repositório

mesmo repositório

oosh-lint

bruno-de-queiroz/oosh

Lint oosh CLI annotations for errors and warnings. Use /oosh-lint <cli> [module] to check annotation syntax, flag types, variable naming, and structural issues. Offers --fix for auto-correction. Trigger when the user wants to validate or fix oosh annotations.

2026-04-0433

oosh

bruno-de-queiroz/oosh

Scaffold a new bash CLI using the oosh framework. Use /oosh <name> to generate a complete CLI with entry point, tab completion, modules directory, and sample modules. Trigger when the user wants to create a new bash CLI tool or shell script with flags and completion.

2026-04-0433

oosh-trace

bruno-de-queiroz/oosh

Profile tab-completion performance for an oosh CLI. Use /oosh-trace <cli> [module] to measure shortlist and help timing, flag slow dynamic enum resolvers. Trigger when the user wants to check or optimize oosh completion speed.

2026-04-0433

name	oosh-module
description	Create a new module for an oosh CLI. Use /oosh-module <cli> <module> to generate an annotated .sh file in the CLI's modules directory. Trigger when the user wants to add a command, module, or feature to an existing oosh CLI.

/oosh-module — Create a new module

Create a new module file in the CLI's modules directory.

Steps

Determine the modules path: ~/.<cli>/modules/ (default) — if the CLI was generated to a custom path, ask the user
Ask what commands and flags the module should expose
Write <module>.sh following the conventions below
Run oosh lint <cli> <module> to validate the new module

Conventions

Read references/annotations.md in this skill directory for the full annotation reference and module template.

Key rules:

File starts with #!/bin/bash and #@module <Name> - <description>
Import the engine: . ${MODULES_DIR}/../oo.sh
Variable names: UPPER_SNAKE_CASE, prefixed with module name (e.g., DEPLOY_ENV in deploy.sh)
End with main $0 "$@"
No sed, awk, grep in hot paths — bash builtins only
Bash 3.2 compatible