القائمة
Stage and commit current changes for Button2 — checks for needed CHANGELOG/README/CLAUDE.md updates, creates a branch if on master, writes a commit message, and commits
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Cut a new Button2 release — suggests version bump based on change type, updates version files and CHANGELOG, commits, tags, pushes, creates a GitHub release, and publishes to PlatformIO
Compile Button2 examples across Arduino platforms using arduino-cli and PlatformIO. Pass a platform name (esp8266, esp32, nano, all) or leave blank to compile all.
Audit README.md against the current Button2 API and recent CHANGELOG entries, then apply any needed updates
Run Button2 test suites via PlatformIO. Optionally pass a suite name (basics, clicks, callbacks, states, configuration, multiple) or platform (esp8266, esp32, nano). Defaults to all suites on ESP8266.
| name | commit |
| description | Stage and commit current changes for Button2 — checks for needed CHANGELOG/README/CLAUDE.md updates, creates a branch if on master, writes a commit message, and commits |
Commit the current working changes. Follow these steps:
Run git diff --stat and git status to see what files are modified or untracked. Read the diffs for any changed source files (src/, test/, examples/) to understand the nature of the changes.
Run git branch --show-current. If on master or main:
fix/was-pressed-for, feat/new-callback, docs/readme-update)git checkout -b <branch-name>If any source files (src/, test/, examples/) changed, check whether CHANGELOG.md's ## Unreleased section already documents those changes. If not, add the missing entries following the established format:
**Fixed (Issue #N)**: ... for bug fixes**Added**: ... for new API or features**Changed**: ... for behavioral changes**Internal**: ... for refactors, test additions, infra with no user-visible effectSkip changelog update for whitespace-only, comment, or docs-only changes.
If public API changed (new/removed/renamed functions in src/Button2.h), check whether README.md reflects the change. If not, update the relevant section. Skip for internal or test-only changes.
If a non-obvious pattern, gotcha, or invariant was introduced that future sessions should know about, add a concise note to CLAUDE.md. Do not add obvious or one-off information.
Stage all relevant files:
git add <changed source files> CHANGELOG.md # plus README.md / CLAUDE.md if updated
Write a conventional commit message:
fix: for bug fixesfeat: for new featurestest: for test-only changesdocs: for documentation onlychore: for tooling, config, infraKeep the subject line under 72 characters. Add a short body if the why isn't obvious from the subject.
Run git commit -m "..." and confirm success.