- Open an issue for major changes before writing code
- Do not commit secrets,
.env, exported documents, or local runtime artifacts - Keep the core export workflow stable unless the change explicitly targets behavior
npm install
cp .env.example .envFill in valid Feishu credentials in .env, then use:
npm run list
npm run download
npm test- Prefer small, reviewable pull requests
- Preserve existing logging clarity
- Add or update tests when changing stable local logic
- Update
README.mdwhen behavior, configuration, or permissions change - Update
CHANGELOG.mdfor user-visible changes
- Code is formatted and readable
- No secrets or generated downloads are included
npm testpasses locally- Documentation has been updated where needed