Skip to content

feat: add v0.1 basd coding dispatch repo skeleton#1

Open
damienen wants to merge 3 commits intomainfrom
feature/v0.1-repo-skeleton
Open

feat: add v0.1 basd coding dispatch repo skeleton#1
damienen wants to merge 3 commits intomainfrom
feature/v0.1-repo-skeleton

Conversation

@damienen
Copy link
Copy Markdown
Owner

@damienen damienen commented May 7, 2026

Summary

This PR creates the public basd-coding-dispatch v0.1 repo as a Hermes/OpenClaw-first, provider-agnostic coding dispatch skill for approval-gated AI coding from any channel.

The flagship path is Telegram/mobile or any Hermes/OpenClaw channel as the operator surface, with Codex/Claude-style workers behind an approval-gated workflow.

What changed

  • Added the public basd-coding-dispatch skill and reference workflow docs.
  • Added a real npm CLI/scaffolder with native hermes and openclaw install targets.
  • Made Hermes the default install target and documented OpenClaw as first-class.
  • Added portable/manual adapter docs for other harnesses without overclaiming native support.
  • Added examples for mobile/Telegram dispatch, small fixes, feature builds, and dual-provider review.
  • Added repo hygiene: README, license, contributing/security docs, issue templates, PR template, changelog, CI, release workflow, llms.txt, and assets.
  • Polished launch metadata and installer checks:
    • approved package/repo description
    • manual adapter tilde expansion
    • clearer doctor labels
    • safer doctor command-status handling for unusual spawn errors
    • GitHub Actions upgraded to latest published actions/checkout@v6 and actions/setup-node@v6

Verification

Local/controller verification passed:

  • npm install --package-lock-only
  • npm run validate
  • npm run smoke-test
  • npm_config_cache=/tmp/npm-cache-basd-coding-dispatch npm pack --dry-run
  • git diff --check
  • temp Hermes install/discovery checks
  • temp OpenClaw install checks
  • real OpenClaw discovery: openclaw skills info basd-coding-dispatch
  • independent Claude review: approved, no blocking findings

PR checks are expected to validate the workflow changes after this push:

  • CI validate
  • GitGuardian Security Checks

Guardrails

Not done in this PR step:

  • no merge to main
  • no npm publish
  • no GitHub release/tag
  • no branch-protection/ruleset change yet

Those need explicit follow-up approval after the PR is green and reviewed.

damienen added 3 commits May 7, 2026 23:54
- Add provider-neutral plan-first coding dispatch skill and references
- Add npm installer/scaffolder CLI with validation and smoke tests
- Add multi-harness integration docs, examples, CI, and OSS governance files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant