apply
Path to an IacPlan JSON from a prior /nyann:plan run, to apply the exact previewed plan.
Sync interval in hours. Default 24.
> /plugin marketplace add thettwe/nyann > /plugin install nyann@nyann-plugins
How it fires
How this command gets triggered: by you, by Claude, or both.
/add-team-sourceContext preview
What this command does when you run it.
Sync interval in hours. Default 24.
name: nyann:add-team-source
description: >
Register a team-profile git source in ~/.claude/nyann/config.json.
Idempotent upsert on --name.
arguments:
- name: name
description: Short slug (becomes the namespace prefix, e.g. `platform-team/base`).
optional: false
- name: url
description: Any git-cloneable URL.
optional: false
- name: ref
description: Branch or tag. Default `main`.
optional: true
- name: interval
description: Sync interval in hours. Default 24.
optional: true**Plugin root:** This is a Claude Code plugin, NOT a CLI tool. Do NOT search via `which`, `npm list`, `pip list`, or `brew list`. This file is at `<plugin_root>/commands/`. All scripts: `<plugin_root>/bin/`. Read the matching `skills/*/SKILL.md` for the full flow.
Wraps `bin/add-team-source.sh`. Does not pull — registration only. Run `/nyann:sync-team-profiles` to fetch. See `skills/add-team-source/SKILL.md` for the upsert semantics and hand-off routing.
ငြမ်း is Burmese for scaffolding. Nyann is the Claude Code plugin that picks expert git defaults for your stack — branching, working hooks (Husky / pre-commit.com / lefthook), commits, releases, CI, docs — then keeps the repo on those rails through every PR
Repo: thettwe/nyann
Path to an IacPlan JSON from a prior /nyann:plan run, to apply the exact previewed plan.
Optional profile name to apply. If provided, skip stack detection's recommendation step and load this profile via bin/load-profile.sh. Fall back to the skill's…
The branch slug (feature/bugfix/hotfix) or version string (release).
If passed, emit the probe results as JSON instead of the human table.
Branch to use as the merge target. Defaults to the profile's primary base branch (auto-resolved through `origin/HEAD`, `main`, or `master`).
Generate a Conventional Commits message from the staged diff and commit after confirmation. Same flow as the natural-language `commit` skill — dispatches here…