Skip to content

Feat improve baked skills for plugin creation #1

Open
javimosch wants to merge 1 commit intomasterfrom
vk/385b-feat-improve-bak
Open

Feat improve baked skills for plugin creation #1
javimosch wants to merge 1 commit intomasterfrom
vk/385b-feat-improve-bak

Conversation

@javimosch
Copy link
Owner

@javimosch javimosch commented Mar 10, 2026

Add backed skill to help agents understand how to add a plugin

Summary by CodeRabbit

  • New Features

    • Added a new plugin creation skill to help users create and validate plugin harness manifests and command mappings.
  • Documentation

    • Updated skill documentation with usage examples demonstrating plugin registry and creation workflows.
  • Tests

    • Extended test coverage for the new plugin creation skill functionality.

Add a new skills entry for plugin harness authoring so agents can follow a standard create/test/publish workflow. Wire it into skills list/get and document it with test coverage.
@coderabbitai
Copy link

coderabbitai bot commented Mar 10, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 24c37a7d-3758-4746-9884-af2a21d0795f

📥 Commits

Reviewing files that changed from the base of the PR and between 1904de2 and 933c8b4.

📒 Files selected for processing (4)
  • __tests__/skills.test.js
  • cli/skills.js
  • docs/features/skills.md
  • docs/plugins.md

📝 Walkthrough

Walkthrough

This PR introduces a new plugin creation skill to the skills module, adding a PLUGIN_CREATION_SKILL_ID constant and buildPluginCreationSkillMarkdown function to generate markdown documentation for creating and validating plugin harnesses. The new skill is registered in the catalog and integrated into the existing skills command handler, with corresponding test coverage and documentation.

Changes

Cohort / File(s) Summary
Core Skills Implementation
cli/skills.js
Added new constant PLUGIN_CREATION_SKILL_ID and function buildPluginCreationSkillMarkdown(options) to generate plugin creation skill documentation. Extended listSkillsMetadata to register the new skill and updated handleSkillsCommand to route requests for the plugin creation skill. Exported both new constant and function in module exports.
Skill Tests
__tests__/skills.test.js
Added test suite for buildPluginCreationSkillMarkdown verifying frontmatter includes correct skill name, dag section rendering when showDag is true, and directive comment presence. Extended listSkillsMetadata test expectations to include plugin-related skill entries. Added test case for plugin creation subcommand retrieval via handleSkillsCommand.
Documentation
docs/features/skills.md, docs/plugins.md
Added usage examples for plugin registry and plugin harness creation skills in the skills documentation. Added reference to plugin creation workflow guidance in the plugins documentation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 A new skill hops into the garden,
Plugin harnesses dance in markdown delight,
With tests and docs, our gifts are bright,
Creating manifests with gentle might! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Feat improve baked skills for plugin creation' clearly describes the main change: adding/improving baked skills for plugin creation. It directly aligns with the changeset which introduces a new skill (buildPluginCreationSkillMarkdown) and integrates plugin creation guidance into the skills system.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch vk/385b-feat-improve-bak

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 933c8b48d5

ℹ️ 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".

]
}

return `---\n${renderYamlObject(frontmatter)}\n---\n\n# Instruction\n\nUse this workflow to create a plugin harness for any CLI:\n\n1. Scaffold a plugin folder with a required manifest:\n\n\`\`\`bash\nmkdir -p my-plugin\n# create my-plugin/plugin.json\n\`\`\`\n\n2. Define plugin metadata and dependency checks in \`plugin.json\`:\n\n- include \`name\`, \`version\`, \`description\`, and \`source\`\n- add \`checks\` for required binaries (for example, \`my-cli\`)\n\n3. Map commands to adapters:\n\n- for selective commands, use \`adapter: \"process\"\` with \`command\`, \`baseArgs\`, \`positionalArgs\`, and optional \`optionalArgs\`\n- for full passthrough, set \`resource: \"_\"\`, \`action: \"_\"\`, and \`adapterConfig.passthrough: true\`\n- prefer JSON output where possible using \`jsonFlag\` and \`parseJson: true\`\n\n4. Add optional post-install indexing (if your plugin syncs remote skills):\n\n- define \`post_install.script\`, optional \`runtime\`, and \`timeout_ms\`\n- keep post-install scripts deterministic and short-lived\n\n5. Test locally and validate behavior:\n\n\`\`\`bash\nsupercli plugins install ./my-plugin\nsupercli plugins show my-plugin\nsupercli plugins doctor my-plugin\n\`\`\`\n\n6. Publish when ready:\n\n\`\`\`bash\nsupercli plugins publish ./my-plugin\n\`\`\`\n\nFor complete field references and real-world examples, see \`docs/plugin-harness-guide.md\`.\n\n# Examples\n\n\`\`\`bash\nsupercli skills get ${PLUGIN_CREATION_SKILL_ID} --format skill.md\nsupercli skills get ${PLUGIN_CREATION_SKILL_ID} --format skill.md --show-dag\n\`\`\``

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Remove publish step from plugin-creation baked skill

The new plugins.harness.create baked skill instructs agents to run supercli plugins publish ./my-plugin, but handlePluginsCommand only supports list, explore, install, remove, show, and doctor (the fallback error in cli/plugins-command.js confirms this), so this step will always fail when agents follow the workflow. Because this skill is meant to be executable guidance, the non-existent subcommand makes the new plugin-creation flow unreliable until either plugins publish exists or the instruction is changed.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant