Skip to content

altertable-ai/altertable-client-specs

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

29 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Altertable Client Specs

License: MIT

Versioned API specifications and agent skills for building and maintaining Altertable open-source SDKs.

Overview

This repository contains pure specifications: requirements, fixtures, constants, and test plans. SDK repositories consume it as a git submodule. Workspace skills read these specs and act on them.

SDK repositories pin a specific version tag of this repo via a specs/ submodule, ensuring every SDK is built against a known, reproducible spec snapshot.

Specs

Skill Description
bootstrap-sdk Fork, clone, and wire up a new SDK repo or update an existing one to a new spec version
build-lakehouse-sdk Build a production-grade Altertable Lakehouse API client in any language
build-product-analytics-sdk Build an Altertable Product Analytics SDK with identity, event tracking, and auto-capture
build-http-sdk HTTP client best practices — connection pooling, keep-alive, timeouts (referenced by build-* skills)
build-readme Write READMEs for SDK repos and monorepo roots following Altertable conventions
maintainer-routine Notification-driven maintainer routine to identify actionable work across Altertable SDK repositories
release-sdk Release SDKs, write changelogs, and publish to language registries
review-pr Review community pull requests against Altertable SDK standards
sync-repos Keep shared configuration, community files, and CI templates consistent across SDK repositories
triage-issues Triage incoming GitHub issues across Altertable SDK repositories

Using This Repo as a Submodule

To consume a pinned version of these specs in an SDK repository:

git submodule add https://github.com/altertable-ai/altertable-client-specs.git specs
git -C specs checkout <spec-tag>
git add .gitmodules specs
git commit -m "chore: add altertable-client-specs submodule at <spec-tag>"

After cloning an SDK repo that already includes this submodule:

git submodule update --init --recursive

Versioning

Spec versions follow Semantic Versioning. Each tag (e.g. v0.1.0) represents a stable, immutable snapshot. SDK repositories pin to a tag — never a branch — to guarantee reproducible builds.

Workspace

Albert, the autonomous AI maintainer of these SDKs, operates from the albert-workspace repository. Operational skills (triage, review, release, sync) live there.

Contributing

  1. Fork this repository
  2. Create a branch: feat/<short-desc> or fix/<issue-number>-<short-desc>
  3. Commit your changes with a clear message
  4. Push to your fork
  5. Open a pull request against main

License

MIT

Links

About

Versioned API specifications and agent skills for building and maintaining Altertable open-source SDKs.

Resources

License

Stars

Watchers

Forks

Packages

 
 
 

Contributors