Skip to content

Add commands to pull AI Skills#2893

Merged
yihao03 merged 14 commits intoMarkBind:masterfrom
yihao03:feat/skill-commands
Apr 16, 2026
Merged

Add commands to pull AI Skills#2893
yihao03 merged 14 commits intoMarkBind:masterfrom
yihao03:feat/skill-commands

Conversation

@yihao03
Copy link
Copy Markdown
Contributor

@yihao03 yihao03 commented Apr 16, 2026

What is the purpose of this pull request?

  • Documentation update
  • Bug fix
  • Feature addition or enhancement
  • Code maintenance
  • DevOps
  • Improve developer experience
  • Others, please explain:

Overview of changes:
As a part of #2869: create skills for MarkBind users, This PR adds a new command: markbind skills that pulls skills for the MarkBind Skills repository and add them to user's MarkBind project root.

We foresee changes made to MarkBind such that the skills will no longer be consistent with actual MarkBind features and/or configurations. Therefore, we have implemented a version control system by writing a .markbind-skills.json file to .agents/skills to keep track of the version of skills that the user has. This allows us to prompt users to update their skills if they are inconsistent with the package.json aiSkillsVersion field.

Anything you'd like to highlight/discuss:
This PR also includes a new package @inquirer/prompts to handle interactive prompt for users to idenfity the coding harnesses used and create symlinks accordingly. This is a step towards #2888

Testing instructions:
Pull this branch and run markbind skills to test out all the commands.

Proposed commit message: (wrap lines at 72 characters)
Add markbind skills command to pull MarkBind Skills from GitHub


Checklist: ☑️

  • Updated the documentation for feature additions and enhancements
  • Added tests for bug fixes or features
  • Linked all related issues
  • No unrelated changes

Reviewer checklist:

Indicate the SEMVER impact of the PR:

  • Major (when you make incompatible API changes)
  • Minor (when you add functionality in a backward compatible manner)
  • Patch (when you make backward compatible bug fixes)

At the end of the review, please label the PR with the appropriate label: r.Major, r.Minor, r.Patch.

Breaking change release note preparation (if applicable):

  • To be included in the release note for any feature that is made obsolete/breaking

Give a brief explanation note about:

  • what was the old feature that was made obsolete
  • any replacement feature (if any), and
  • how the author should modify his website to migrate from the old feature to the replacement feature (if possible).

Copy link
Copy Markdown
Contributor

@MoshiMoshiMochi MoshiMoshiMochi left a comment

Choose a reason for hiding this comment

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

LGTM (again!)

@yihao03 yihao03 merged commit 6d4258e into MarkBind:master Apr 16, 2026
23 checks passed
@github-actions github-actions bot added the r.Minor Version resolver: increment by 0.1.0 label Apr 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

r.Minor Version resolver: increment by 0.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants