skills.rest
FlexNetOS
FlexNetOSOFFICIAL
Explore all skills by this author →
GitHub

kb-commit

Review, validate, and selectively commit knowledge base changes.

Updated Jun 2, 2026
Search Tags:#collaboration#commit#validation#knowledge base#review
One-click install
npx skills add https://github.com/FlexNetOS/envctl --skill kb-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kb-commit
Source: https://github.com/FlexNetOS/envctl/tree/main/.kb/skills/kb-commit
Command: npx skills add https://github.com/FlexNetOS/envctl --skill kb-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of committing workspace changes to a knowledge base, ensuring that changes are validated and reviewed before they are committed.

Core Features & Use Cases

  • Review and Validation: Automatically reviews changes for common issues and provides warnings before committing.
  • Commit Message Generation: Analyzes changes and drafts a concise commit message.
  • Selective Committing: Allows users to commit only the documents they modified, avoiding unintended commits of other agents' work.
  • Use Case: Ideal for teams working on collaborative projects where changes to a knowledge base need to be carefully managed and validated.

Quick Start

Run the 'kb-commit' command with the 'message' and 'pathspecs' arguments to review and commit changes to the knowledge base.

Frequently Asked Questions about kb-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate knowledge base changes before committing them?▼

Validating knowledge base changes before committing involves reviewing modified documents for common issues and generating warnings. This process ensures changes are checked against validation rules and selectively committed only after a successful review.

Can I commit only specific modified documents to a shared knowledge base?▼

Yes, you can selectively commit specific modified documents to a knowledge base. By specifying pathspecs, you avoid committing unintended changes from other agents and ensure only your reviewed work is committed to the collaborative workspace.

How do I automatically generate commit messages for knowledge base updates?▼

Automatically generating commit messages for knowledge base updates requires analyzing the document diffs. The system reviews the changes and drafts a concise message summarizing the modifications, providing a clear history of validated edits.

What's the best way to review workspace changes before a knowledge base commit?▼

The best way to review workspace changes before a knowledge base commit is to use status and diff tools for change analysis. Automating this review detects common issues early, ensuring only validated modifications are committed with accurate messages.

Do I need diff tools to automate knowledge base commits with validation?▼

Yes, you need knowledge base status and diff tools to automate commits with validation. These tools provide the necessary change analysis data to review modifications, detect issues, and selectively commit only the intended document updates.

Related Skills

Explore More Product & Management Skills→
t-miura-024t-miura-024

mt-check-git-diff

Analyze git repository changes and retrieve detailed diffs for modified files.

Community
Intermediate
xdrshjrxdrshjr
1

github-commit-push

Automate GitHub commit and push workflows with SSH-based remote synchronization.

Community
Basic
dawsonblockdawsonblock

doc-coauthoring

Manage collaborative document editing with version control, comment resolution, and merge strategies.

Community
Intermediate
yanochka11yanochka11

commit

Generate conventional git commit messages with validated types and issue references.

Community
Intermediate