analyze-code
CommandAnalyze code quality, identify issues, and suggest improvements.
Design and hire a new crew member by describing the job
> /plugin marketplace add nimbalyst/nimbalyst> /plugin install nimbalyst-wiki@nimbalyst
description: Design and hire a new crew member by describing the job
Hire a crew member for: $ARGUMENTS
A crew member is a long-running agent with a name, a role, a personality, a schedule of shifts, and a job description. Each shift runs as an ordinary session in this project. You design the member with the user, then write it with the `crew_hire` tool.
If the job above is empty, ask the user what the member should do. Then look at what already exists so the new member fits in:
Use your interactive question tool, in one prompt where you can, for anything the job does not already settle:
Skip a question the user has already answered. Do not ask about the model unless the user brings it up.
The file is YAML frontmatter under a `crew:` key, then the job as the markdown body:
---
crew:
name: Ada
role: Architect
color: "#7c6cf2"
provider: claude-code
model: sonnet
personality: Calm, dry, allergic to accidental complexity. Speaks in short paragraphs and names the specific file and function.
schedule:
- daily: "18:30"
prompt: Review today's merged work for architectural drift.
- weekly:
days: [monday, wednesday, friday]
time: "09:00"
prompt: Sweep the tracker for stale design decisions.
notify:
maxLevel: flag
quietHours: "22:00-08:00"
budget:
tokensPerWeek: 60000000
shiftsPerDay: 6
---
You are the project's architect. Each evening, read what changed today and look for problems that are cheap now and expensive later.
- ...Field rules (the tool rejects anything else):
Write the body as direct instructions to the member: what each shift is for, what counts as worth flagging, what it must not do, and where it keeps any artifact it owns. Bullets, one idea each. The member already has a journal, long-term notes, and tools to flag the user and adjust its own schedule, so don't explain those.
Show the user the full draft and ask whether to hire as is or change something. When they approve, call `crew_hire` with the whole file as `definition`. If the result is a validation error, fix the named fields and call again without asking the user, unless the fix changes something they chose.
On success, tell the user the member's name, where the file lives, and when its first shift runs. It appears in the Crew panel's roster, where they can pause it, start a shift, or open the file to edit it.
Nimbalyst - The open-source visual workspace for Claude Code, Codex, and OpenCode. Run multiple coding agents in parallel, edit their work visually in markdown, mockups, and diagrams, and track tasks. Free, MIT-licensed desktop app for macOS, Windows, Linux, with mobile companion for iOS and Android.
Analyze code quality, identify issues, and suggest improvements.
Audit recent AI coding sessions to find repeated mistakes, speed losses, and missed Nimbalyst tool usage — then propose harness…
Triage pnpm audit findings and produce a prioritized, supply-chain-cautious package-update plan, then apply approved batches
Survey recently triaged GitHub issues, propose the ones safe to fix without a product decision, and fan the selected ones out to…
Gather details and draft an actionable bug report for developers.
Shortcut for "continue working" — pick the work in flight back up exactly where it stopped and keep going until it is done or…