lechao365
Community@lechao365
lechao365 provides an embedded-device development pipeline for Raspberry Pi 5 codebases, covering workspace sync, ADB incremental deployment, verification loops, and git baseline promotion.
Agent Skills by lechao365
Showing 10 vetted skills indexed across 1 GitHub repositories.
lechao365workspace-verify
Syncs code to workspace, builds incrementally, pushes via adb, and writes verification receipts.
lechao365sync-code-to-workspace
Restores a diverged AOSP and kernel workspace to the archived code baseline via plan-based synchronization.
lechao365publish-main-base
Orchestrates verified dev-to-main baseline promotion with board validation and rollback.
lechao365sync-code-to-doc
Converts code/rpi5 git diffs into chapter-level incremental documentation updates.
lechao365loop-engineering
Manages verification convergence loops with fingerprint-based failure attribution and retry accounting.
lechao365git-works-push
Commits working tree changes with AI-generated Chinese messages and pushes to origin dev.
lechao365revert-modify-from-main-base
Resets the dev branch to the origin/main baseline with force push and revert receipts.
lechao365opencode-server
Hosts OpenCode WebUI as a systemd user service with Tailscale HTTPS access.
lechao365cross-device-emit
Generates validated CDP batch text from repository diffs for cross-device code modification workflows.
lechao365cross-device-apply
Applies CDP batches to code edits, runs workspace verification, and pushes results.
Frequently Asked Questions About lechao365
FAQPage SchemaWhat tasks can I perform using lechao365's skills?▼
You can synchronize code to a Raspberry Pi 5 workspace, run incremental compilation and ADB pushes, execute verification loops with failure fingerprinting, generate Chinese commit messages and push to origin dev, promote validated baselines to main, revert dev to main when fixes fail, and sync code diffs into structured documentation updates.
Who are these skills designed for?▼
Embedded Linux developers and engineers maintaining a Raspberry Pi 5 codebase across multiple machines. The emit/apply split suits users who analyze context on a strong-model remote device and apply edits on a local device connected to the development board via ADB.
How does the cross-device emit/apply workflow operate?▼
The emit device analyzes repository context and generates a self-checked CDP batch as plain text, which the user copies to the apply device. The apply device parses the batch, edits the dev code, regenerates the manifest, triggers workspace-verify, and pushes results via git-works-push.
What infrastructure does the opencode-server skill set up?▼
It hosts the OpenCode WebUI as a systemd user service on WSL2, configures a Tailscale serve HTTPS reverse proxy, and outputs a tailnet URL accessible from a phone, providing the web entry point for cross-device emit/apply collaboration.
What safeguards exist before promoting code to the main baseline?▼
publish-main-base runs harness self-checks, routes unverified changes into on-device loop verification, converges fixes with retry counting, synchronizes documentation, and registers a candidate before promotion. Any stage that cannot be repaired blocks the promote to main entirely.