automaintainer: search for and add new CLI tools as bundled plugins to supe…#3
Conversation
Gum (github.com/charmbracelet/gum, 18k+ stars) is a Go CLI tool that lets you style, format, and render text in shell scripts. Features include color styling, markdown formatting, table rendering, file picking, text writing, and interactive prompts. - plugin.json: 7 commands covering style, format, table, join, write, file pick, and passthrough - meta.json: registry metadata with has_learn: true - install-guidance.json: brew/go install/binary download instructions - skills/quickstart/SKILL.md: agent usage guide
Dotbot (github.com/anishathalye/dotbot, 7k+ stars) is a Python CLI tool that bootstraps dotfiles using declarative YAML/JSON configs. Supports link, create, shell, clean directives with dry-run and plugin support. - plugin.json: 6 commands covering install run, link, shell, create, clean, and passthrough - meta.json: registry metadata with has_learn: true - install-guidance.json: pip/brew/uv install instructions - skills/quickstart/SKILL.md: agent usage guide
📝 WalkthroughWalkthroughThis PR introduces two independent plugin integrations for supercli: dotbot (dotfile management and automation) and gum (terminal styling and formatting). Each plugin includes installation guidance, a manifest wiring commands to adapters, and user-facing quickstart documentation. ChangesDotbot Plugin Integration
Gum Plugin Integration
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 72a39fe475
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "adapterConfig": { | ||
| "command": "gum", | ||
| "baseArgs": ["style"], | ||
| "missingDependencyHelp": "Install gum: brew install gum", | ||
| "passthrough": true |
There was a problem hiding this comment.
For exact wrapped commands such as gum style apply --text hi --bold, passthrough: true prevents the declared SuperCLI flags from reaching gum: in the Node CLI only remainingPositionalArgs are copied to __rawArgs (cli/supercli.js 981-984), so --text, --bold, etc. are dropped; in the preferred Zig CLI the raw passthrough slice starts at the resource (supercli-zig-cli/src/main.zig 980), so this becomes gum style style apply .... I checked gum's command syntax (gum style [<text> ...] [flags]), so these wrappers need normal flag/positional mapping rather than passthrough.
Useful? React with 👍 / 👎.
| "args": [ | ||
| { | ||
| "name": "config", | ||
| "type": "string", | ||
| "required": true, | ||
| "description": "Path to configuration file" |
There was a problem hiding this comment.
The dotbot wrapper exposes a required config argument, but the process adapter will emit it as --config <file> for the non-passthrough subcommands and will reject a bare positional file because adapterConfig.positionalArgs is not set. I checked dotbot's documented invocation, which uses dotbot -c <path> / --config-file, so commands like dotbot install link --config install.conf.yaml cannot select the requested config and fail before running the intended directive.
Useful? React with 👍 / 👎.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (3)
plugins/dotbot/skills/quickstart/SKILL.md (1)
10-17: 💤 Low valueConsider documenting the version command.
The plugin manifest (plugin.json) defines a
dotbot self versioncommand (lines 29-41), but it's not listed in the Commands section of this documentation.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@plugins/dotbot/skills/quickstart/SKILL.md` around lines 10 - 17, The Commands section in SKILL.md is missing documentation for the `dotbot self version` command declared in plugin.json; update SKILL.md to add an entry (e.g., "`dotbot self version` — Show the plugin/tool version") under Commands so it documents the `dotbot self version` command referenced in plugin.json (lines that define the command).plugins/dotbot/install-guidance.json (2)
1-13: 💤 Low valueVerify that install-guidance.json duplication is intentional.
The content of
install-guidance.jsonis duplicated verbatim inplugin.json(lines 12-24). This creates a maintenance burden if installation guidance changes later.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@plugins/dotbot/install-guidance.json` around lines 1 - 13, The install guidance is duplicated between install-guidance.json and plugin.json; remove the duplication by keeping the canonical installation metadata in plugins/dotbot/install-guidance.json and deleting the redundant "install_steps"/"note" block from plugins/dotbot/plugin.json (or conversely move plugin.json to reference the install-guidance.json content), update plugin.json to reference or import the guidance instead of copying it, and ensure the unique JSON keys "install_steps", "binary", "check", and "note" remain present only in the canonical install-guidance.json so future updates require changing a single file.
12-12: 💤 Low valueMinor inconsistency in star count.
Line 12 states "7k+ stars" while
plugin.jsonline 23 states "7k stars" (without the +). Consider using consistent formatting across files.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@plugins/dotbot/install-guidance.json` at line 12, The "note" value in install-guidance.json currently says "7k+ stars" while plugin.json uses "7k stars"; make these consistent by choosing one format and updating the JSON values—edit the "note" key in install-guidance.json and the "stars" (or equivalent) key in plugin.json so both use the same wording (either "7k+ stars" or "7k stars") and ensure punctuation/spacing matches across files.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@plugins/dotbot/plugin.json`:
- Around line 80-84: The "plugin" argument in plugin.json is defined as type
"string" but the description and usage require multiple values; update the
"plugin" schema entry (the "plugin" property) to support multiple values by
changing its type to "array" and adding an "items": {"type":"string"}
specification so callers can pass multiple plugins, and ensure the description
stays accurate; if your process adapter cannot map arrays to repeated flags,
instead update the same "plugin" description to explicitly state the required
comma-separated format or adapt the invocation logic that consumes this "plugin"
property.
- Around line 54-60: The dotbot install command wiring is wrong: the declared
arg "config" is validated but never passed to dotbot because adapterConfig has
"passthrough": true and empty baseArgs; update the dotbot.install.run command's
adapterConfig to stop passthrough and map the arg by adding baseArgs:["-c"] and
positionalArgs:["config"] so the validated "config" value is emitted as dotbot
-c <file>; alternatively remove the named "config" arg and document that users
must supply -c <file> in passthrough mode. Also fix the misleading
args.name="plugin" description (either remove or reword it) because in
passthrough mode it doesn’t affect the underlying dotbot invocation.
In `@plugins/gum/plugin.json`:
- Around line 246-264: Update the inaccurate description and arg help for the
gum write command: in the plugin JSON (entry with "namespace": "gum",
"resource": "write", "action": "text") replace the "description" value to say
that gum opens an interactive multi-line text area and outputs the entered text
to stdout (not writing to a file or reading from stdin), and update the
"content" arg's "description" to match (e.g., "Optional initial content; gum
opens an interactive editor and prints the result to stdout"). Also apply the
same corrected wording in skills/quickstart/SKILL.md where the gum write
behavior is described so both locations consistently state that gum prints
entered text to stdout from an interactive editor.
---
Nitpick comments:
In `@plugins/dotbot/install-guidance.json`:
- Around line 1-13: The install guidance is duplicated between
install-guidance.json and plugin.json; remove the duplication by keeping the
canonical installation metadata in plugins/dotbot/install-guidance.json and
deleting the redundant "install_steps"/"note" block from
plugins/dotbot/plugin.json (or conversely move plugin.json to reference the
install-guidance.json content), update plugin.json to reference or import the
guidance instead of copying it, and ensure the unique JSON keys "install_steps",
"binary", "check", and "note" remain present only in the canonical
install-guidance.json so future updates require changing a single file.
- Line 12: The "note" value in install-guidance.json currently says "7k+ stars"
while plugin.json uses "7k stars"; make these consistent by choosing one format
and updating the JSON values—edit the "note" key in install-guidance.json and
the "stars" (or equivalent) key in plugin.json so both use the same wording
(either "7k+ stars" or "7k stars") and ensure punctuation/spacing matches across
files.
In `@plugins/dotbot/skills/quickstart/SKILL.md`:
- Around line 10-17: The Commands section in SKILL.md is missing documentation
for the `dotbot self version` command declared in plugin.json; update SKILL.md
to add an entry (e.g., "`dotbot self version` — Show the plugin/tool version")
under Commands so it documents the `dotbot self version` command referenced in
plugin.json (lines that define the command).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: b621f7ca-62b9-4078-bcc8-8c92ac14b3c2
📒 Files selected for processing (8)
plugins/dotbot/install-guidance.jsonplugins/dotbot/meta.jsonplugins/dotbot/plugin.jsonplugins/dotbot/skills/quickstart/SKILL.mdplugins/gum/install-guidance.jsonplugins/gum/meta.jsonplugins/gum/plugin.jsonplugins/gum/skills/quickstart/SKILL.md
|
Automaintainer Review Verdict: APPROVED Summary: PR adds two new bundled plugins (gum 18k★, dotbot 7k★) following the established plugin structure. Changes are additive — 8 new files, 0 modified — and structurally consistent with existing plugins. CI note: Test failure is pre-existing ( External review feedback considered:
Verdict: APPROVED — correct, safe, adds real value. |
|
Approved by automaintainer review team — auto-merging |
|
To use Codex here, create an environment for this repo. |
|
For the two minor items I flagged, would you like me to open follow-up GitHub issues to track them so they don't get lost?
Just say the word and I'll create them. ✅ Actions performedComments resolved. Approval is disabled; enable |
|
Approved by automaintainer review team — auto-merging |
|
Automaintainer Review Verdict: APPROVED (retrospective — PR already merged) Summary: Two new plugins (gum 18k★, dotbot 7k★) added following established plugin structure. 8 new files, 0 modified, 704 additions. External review concerns addressed:
Verdict: Core functionality is sound. Minor issues flagged above are suitable for a follow-up PR. |
|
To use Codex here, create an environment for this repo. |
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
# Create issue 1: dotbot plugin field type
gh issue create \
--repo javimosch/supercli \
--title "fix(dotbot): plugin field should be array type in plugin.json" \
--assignee javimosch \
--body "## Summary
In \`plugins/dotbot/plugin.json\`, the \`plugin\` field is currently a plain string but should be an array to support multiple values (consistent with how multi-value fields are expected to work in plugin manifests).
## Context
Flagged during review of `#3` (already merged). The passthrough and catchall commands provide working paths in the meantime, so this is a non-blocking cleanup.
## Requested Fix
Change the \`plugin\` field from a string to an array type in \`plugins/dotbot/plugin.json\`.
---
Backlink: https://github.com/javimosch/supercli/pull/3
Raised by: `@javimosch` (automaintainer retrospective review)"
echo "---"
# Create issue 2: gum write description inaccuracy
gh issue create \
--repo javimosch/supercli \
--title "fix(gum): correct gum write command description in plugin.json and SKILL.md" \
--assignee javimosch \
--body "## Summary
The \`gum write\` command is described as a file writer in \`plugins/gum/plugin.json\` and \`plugins/gum/skills/quickstart/SKILL.md\`, but it is actually an interactive TUI multi-line text input component — it does not write files directly.
## Context
Flagged during review of `#3` (already merged). This is a documentation inaccuracy that could mislead users about the command's actual behavior.
## Requested Fix
Update the description of the \`gum write\` command in:
- \`plugins/gum/plugin.json\`
- \`plugins/gum/skills/quickstart/SKILL.md\`
to accurately reflect that it provides an interactive multi-line text input TUI, not a file-writing utility.
---
Backlink: https://github.com/javimosch/supercli/pull/3
Raised by: `@javimosch` (automaintainer retrospective review)"Length of output: 2017 Both follow-up issues have been created and assigned to you,
Both are backlinked to this PR for traceability. 🐇 |
1 participant
Automated maintenance run by automaintainer.
Focus: search for and add new CLI tools as bundled plugins to supercli. For each plugin: search GitHub for non-interactive CLI tools (stars>100, rust/go/python), create plugin files (plugin.json, meta.json, install-guidance.json, skills/quickstart/SKILL.md), validate JSON, commit with conventional commit message. Target 2 plugins per session.
Branch:
am/am-0e131c-tfuausSummary by CodeRabbit