Imported from baneeishaque/ljt-520_openclaw-backup (skills/jontsai/spacesuit/AGENTS.md). Install upstream with npx skills add baneeishaque/ljt-520_openclaw-backup --skill spacesuit. Copyright stays with the author.

AGENTS.md — Development Guide for openclaw-spacesuit

This file is for REPO CONTRIBUTORS, not workspace users. The file at base/AGENTS.md is the framework template that gets installed into user workspaces. This file lives at the repo root and provides development rules for this repo itself.

⚠️ Golden Rule: This is OPEN SOURCE

NEVER add any of the following to this repo:

• Personal names, usernames, or identifiers
• API keys, tokens, or secrets (even examples that look real)
• Machine names, hostnames, IP addresses
• Company names, project names, or internal references
• Anything that ties this repo to a specific person or organization

All base files and templates must be generic — useful for ANY OpenClaw user, anywhere.

Run make test before every commit to catch accidental leaks.

Repository Structure

openclaw-spacesuit/
├── base/              # Framework content (inserted between SPACESUIT markers)
├── templates/         # Full-file templates with placeholders + user sections
├── scripts/           # install.sh, upgrade.sh, diff.sh
├── tests/             # Unit tests (bash)
├── SKILL.md           # ClawHub package metadata
├── VERSION            # Semver version string
├── Makefile           # Dev + user targets
├── CHANGELOG.md       # Release notes
└── AGENTS.md          # THIS FILE (dev guide, not installed to workspaces)

Development Rules

1. Keep base/ and templates/ in sync

Every base file has a corresponding template. If you edit base/X.md, verify that templates/X.md.tmpl still references it correctly via {{SPACESUIT_BASE_*}} placeholders.

2. Section markers must be consistent

Templates use these markers to wrap framework content:

<!-- SPACESUIT:BEGIN SECTION_NAME -->
{{SPACESUIT_BASE_SECTION_NAME}}
<!-- SPACESUIT:END -->

• SECTION_NAME must match the key in install.sh's BASE_MAP and upgrade.sh's SECTION_MAP
• Begin marker includes the section name; end marker is always just <!-- SPACESUIT:END -->
• Never nest markers

3. Scripts must work from installed path

When installed via ClawHub, this repo lives at skills/spacesuit/ inside a workspace. All scripts must work when invoked from that path:

skills/spacesuit/scripts/install.sh
skills/spacesuit/scripts/upgrade.sh

Use $SCRIPT_DIR and relative paths, never hardcoded absolute paths.

4. Test before committing

make test

This runs all tests in tests/. Every PR must pass. The test suite checks:

• Install/upgrade functionality
• Marker integrity across base/ and templates/
• No private data in any tracked file

5. Follow conventional commits

feat: add new base section for X
fix: preserve trailing newlines during upgrade
docs: update SKILL.md description
test: add upgrade idempotency test
chore: bump version to 0.2.0

6. Version bumping

• Update VERSION file (semver: MAJOR.MINOR.PATCH)
• Update version in SKILL.md metadata table
• Add entry to CHANGELOG.md

Adding a New Managed File

1. Create base/NEWFILE.md with the framework content
2. Create templates/NEWFILE.md.tmpl with markers + user sections
3. Add the placeholder mapping to scripts/install.sh (BASE_MAP)
4. Add the section mapping to scripts/upgrade.sh (SECTION_MAP and TARGET_MAP)
5. Add tests for the new file
6. Update SKILL.md "Files Managed" table

Testing

make test              # Run full test suite
tests/run_tests.sh     # Same thing, directly
tests/test_install.sh  # Run a single test file

Tests create temporary directories and clean up after themselves. They should be safe to run anywhere.