Question 1

How do I share Nostromo commands with my team?

Accepted Answer

Use the 'dock' feature to add remote manifest sources like Git repositories, then run 'sync' to update commands. This allows centralized management and distribution of command sets across team members.

Question 2

Nostromo vs standard shell aliases: which should I use?

Accepted Answer

Nostromo is better for hierarchical, complex commands with substitutions and team sharing, while standard aliases suffice for simple, one-off shortcuts without the extra tool dependency.

Question 3

How to create a command tree in Nostromo?

Accepted Answer

Use keypaths with 'add cmd', like 'nostromo add cmd foo.bar.baz "echo hello"', to build parent-child relationships. You can visualize it with 'nostromo show' for a tree view.

Question 4

Does Nostromo work on Windows or with fish shell?

Accepted Answer

It's untested and may not work reliably; the README notes compatibility only with MacOS and bash/zsh, so Windows or fish users might encounter issues or need workarounds.

Question 5

Can I run Python scripts directly with Nostromo?

Accepted Answer

Yes, use the '--code' and '--language' flags to execute code snippets in Python, Ruby, JavaScript, or Perl, but complex multiline scripts require careful YAML escaping in the manifest.

Question 6

What happens if commands conflict in multiple docked manifests?

Accepted Answer

Nostromo aggregates commands, but conflicts are not automatically resolved; you may need to manually edit manifests or use 'undock' to remove sources, as syncing can reintroduce conflicts.

nostromo

What is nostromo?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions