Thank you for your interest in contributing to Taiwan Invoice Skills.
- Use GitHub Issues to report bugs or suggest features.
- Include steps to reproduce the issue, expected behavior, and actual behavior.
- For API-related issues, specify which provider (ECPay, SmilePay, or Amego) is affected.
- Fork the repository.
- Create a feature branch from
main:git checkout -b feature/your-feature-name
- Make your changes.
- Test your changes with the included test scripts:
python taiwan-invoice/scripts/test-invoice-amounts.py
- Commit with a clear message:
git commit -m "Add: description of your change" - Push and open a Pull Request.
Use the following prefixes:
Add:new feature or fileFix:bug fixUpdate:improvement to existing featureRemove:removed feature or fileDocs:documentation only changeRefactor:code change that neither fixes a bug nor adds a feature
- TypeScript examples should follow standard TypeScript conventions.
- Python scripts should follow PEP 8.
- Markdown files should use consistent heading levels and no trailing whitespace.
- Do not use emoji in any files.
When updating API reference documents in taiwan-invoice/references/:
- Verify changes against the official provider documentation.
- Include the date of verification.
- Update all three platform copies (
.claude/skills/,.cursor/skills/,.agent/skills/).
When modifying taiwan-invoice/SKILL.md:
- Keep the file under 500 lines.
- Ensure YAML frontmatter fields are valid for all supported platforms.
- Test that the skill loads correctly on at least one platform.
taiwan-invoice/ # Source of truth
.claude/skills/ # Claude Code (auto-discovered)
.cursor/skills/ # Cursor (auto-discovered, also reads .claude/skills/)
.agent/skills/ # Google Antigravity (auto-discovered)
Changes should be made to taiwan-invoice/ first, then synced to platform directories.
By contributing, you agree that your contributions will be licensed under the MIT License.