Lark CLI Dev Hub for Openclaw

A development knowledge system backed by Feishu/Lark Base, Docs, Tasks, and Whiteboard to streamline bug resolution, task state tracking, and release evidence.

afengzi
v0.1.2
May 20, 2026
0
777
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install lark-cli-devhub

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install lark-cli-devhub using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Lark CLI Dev Hub?

Lark CLI Dev Hub is a powerful workspace integration tool designed to bridge the gap between active software development and enterprise collaboration suites like Feishu and Lark. By using this tool alongside Openclaw Skills, software development teams can seamlessly capture project facts, log bug evidence, write down decisions, and preserve release history in centralized document hubs without leaving their terminal or IDE environment.

This skill establishes a systematic structure where Feishu Base acts as the structured source of truth, Docs hold extensive technical details, and interactive boards act as visual references. By implementing this integration, teams leverage AI agent memory to streamline collaboration preferences while maintaining rigid project integrity and comprehensive development history.

Lark CLI Dev Hub Use Cases

  • Preventing Bug Resolution Redundancy: Developers can query past bug investigations, symptom keywords, and resolved issues prior to starting a debug cycle.
  • Enforcing Main-Branch Discipline: Requiring valid release logs, outbox entries, or structured bypass arguments before pushing to main/master branches.
  • Automating AI Run and Release Summaries: Logging critical execution run details and artifact evidence directly to the team's enterprise dashboard.
  • Building a Developer Knowledge Hub: Ensuring pitfalls and playbook guidelines are instantly cataloged as reusable documentation inside Feishu/Lark channels.

How Lark CLI Dev Hub Works

  1. Query & Context Search: Before starting code modification, the developer or AI agent issues a search command against local and cloud indexes to locate relevant historical issues and decisions.
  2. Context-Aware Fixing: The system loads previous playbooks and pitfalls to guide the debugging process, ensuring recurring issues are resolved efficiently.
  3. Record Logging: Post-fix, the system automatically formats and writes JSON payloads representing bugfixes, run summaries, and updated playbooks.
  4. Local Staging: Changes are written to the local staging directory under the project-local outbox and receipts configuration.
  5. Sync & Release Enforcement: Before changes are pushed upstream, pre-push hook checks verify documentation states, syncing pending outbox changes to the cloud repository via Openclaw Skills mechanisms.

Lark CLI Dev Hub Setup

Ensure you have the required dependencies (lark-cli, python3, and git) installed on your system. Next, configure the CLI home directories:

# Define the local home directory for Dev Hub CLI operations
export DEVHUB_HOME="${DEVHUB_HOME:-$HOME/.codex/devhub}"

# Perform a lookup for historical project issues
python3 "$DEVHUB_HOME/bin/devhub.py" search --project "$(basename "$PWD")" --query "symptom area keywords"

# Record standard development metrics and outcomes
python3 "$DEVHUB_HOME/bin/devhub.py" record-bugfix --payload /tmp/devhub-bugfix.json
python3 "$DEVHUB_HOME/bin/devhub.py" record-ai-run --payload /tmp/devhub-ai-run.json
python3 "$DEVHUB_HOME/bin/devhub.py" record-release --payload /tmp/devhub-release.json

# Synchronize pending offline transactions to your Lark workspaces
python3 "$DEVHUB_HOME/bin/devhub.py" sync-outbox --cwd "$PWD"

The config details default to $HOME/.codex/devhub/config.json.

Lark CLI Dev Hub Data Schema & Taxonomy

The directory layout and file structures managed by Lark CLI Dev Hub align developer codebases with cloud databases.

Directory Layout

Directory Path Purpose
$HOME/.codex/devhub/config.json Configuration values, API end-points, and project definitions.
.devhub/receipts/ Local confirmation files generated after a successful cloud sync.
.devhub/outbox/ Local transaction storage containing pending updates to write to Feishu.

Data Taxonomy & Routing Keys

For deeper domain-specific workflows, the system routes data payloads to specialized sub-modules built for Openclaw Skills:

  • lark-cli-devhub-base: Manages Base schemas, dashboards, and structured AI lookup queries.
  • lark-cli-devhub-docs-wiki: Handles long-form page trees, documentation guides, and Wiki nodes.
  • lark-cli-devhub-taskflow: Directs task lists, issue tracking updates, and state changes.
  • lark-cli-devhub-whiteboard: Manages architectural representations and text summary overlays.
  • lark-cli-devhub-drive: Handles file synchronization, asset directories, and metadata imports.

Lark CLI Dev Hub Advanced Features

  • Pre-Push Integrity Checks: Hooks reject main-branch push requests unless backed by a registered receipt, a pending outbox entry, or an explicit skip directive (e.g., # kb-skip: reason).
  • Shadow Mode Guardrails: Enables teams to test synchronization routines without disrupting development, printing warnings first before enforcing writeback policies.
  • Domain-Specific Split Routers: Seamless delegation to dedicated micro-skills for calendars, spreadsheet audits, automated approvals, OKR mappings, and VC meeting action items.
  • Offline-First Resilience: Stages updates in local outboxes for bulk synchronization, protecting workflow continuity when network connections are spotty.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*