EverMind

Opens a GitHub pull request from a scoped branch to `main` using the repository’s template. It checks that `make ci` passes, pushes the branch, and guides completion of the summary, change area, verification, checklist, and reviewer notes.

• Opening a pull request for a completed change
• Filling out the repository’s PR template
• Recording CI and manual verification results

Review the current Git changes and recent history, then create a focused commit with a Conventional Commits message. The skill helps stage only related files, follow the required format, and address hook failures before committing.

• Creating a commit for a focused code change
• Staging only related files from a mixed working tree
• Writing a Conventional Commits message

Creates a scoped Git branch from the updated `main` branch using the project’s naming convention. It selects a prefix for feature work, fixes, docs, CI, maintenance, or refactoring, then adds a concise lowercase, hyphenated name.

• Starting a feature branch
• Creating a bug fix branch
• Preparing a docs or CI change

Prepare and publish a versioned everos release to PyPI. The skill guides version and changelog updates, the tag-triggered workflow, its approval step, and review and publication of the resulting GitHub Release draft.

• Preparing a patch, minor, or major release
• Publishing a release candidate to PyPI
• Reviewing and publishing the GitHub Release draft

Guide developers through adding a persisted business memory type. Choose Markdown, SQLite, and LanceDB storage and a Markdown file strategy, then wire up schemas, repositories, and writers across the layers the data needs.

• Adding a new persisted business record type
• Choosing storage for searchable memory
• Wiring a daily Markdown log with database indexes