jplearn-release-github
JPLearn CI, packaging/release and GitHub issue procedures moved from root CLAUDE.md - why the GitHub workflows use a self-hosted Windows runner, their local equivalents (scripts/dev.py --full, npm run make:release, scripts/bundle_python.ps1), and the gh issue list/create commands for the repo. Use when building an installer or release, editing .github/workflows or scripts/bundle_python.ps1, asking whether CI ran or needs to, or listing/filing GitHub issues.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- jplearn-release-github
- description
- JPLearn CI, packaging/release and GitHub issue procedures moved from root CLAUDE.md - why the GitHub workflows use a self-hosted Windows runner, their local equivalents (scripts/dev.py --full, npm run make:release, scripts/bundle_python.ps1), and the gh issue list/create commands for the repo. Use when building an installer or release, editing .github/workflows or scripts/bundle_python.ps1, asking whether CI ran or needs to, or listing/filing GitHub issues.
03 SKILL.md 正文
JPLearn release, CI and GitHub
Moved verbatim from the root CLAUDE.md ("Commands" and "GitHub").
CI workflows and their local equivalents
Both GitHub workflows target a self-hosted Windows runner (runs-on: [self-hosted, windows])
because hosted Actions minutes are unavailable on this account — if no runner is registered
against the repo, they simply never start. Either way they have local equivalents, so neither
needs CI to run:
python scripts/dev.py --full covers every step of electron-packaged-smoke.yml, and
npm run make:release produces the same installer release.yml uploads (it calls
scripts/bundle_python.ps1, which the workflow also calls — keep the bundling logic
there rather than inline in the YAML). Both rebuild the bundle with -Force and pinned packages,
and make:release then runs the packaged smoke (audit 13, F3).
Installed copies update from GitHub Releases (audit 13, F8). A release that updates them must be
a published, non-prerelease release tagged v<package.json version>, the version a plain x.y.z,
carrying JPLearn-Installer.exe, RELEASES and the *-full.nupkg; README "Releases and updates"
has the local gh release create command. Robbie decides when a release is published.
GitHub issues
gh issue list --repo NeedMeSomeAnimeTiddy/JPLearn --limit 5
gh issue create --repo NeedMeSomeAnimeTiddy/JPLearn --title "..." --body "..." --label "bug|refactor|enhancement"
AGENTS.md also describes the GitHub-issue-automation workflow (written for the opencode
harness; its tool names don't map 1:1 to Claude Code).
04 同仓库更多 Skills
validate-system-integrity
Runs system integrity checks across Domain and Data layers — tests, arch, SRS, and DB checks.
simulate-srs-path
Simulates SRS interval progression for a learning item using deterministic logic.
run-study-session
Executes a full study session using due items from the system and applies SRS logic.
reset-database
Resets the SQLite database schema to a clean state for development or testing.
playwright-browser
Persistent browser automation protocol — 3-attempt rule, verified target selectors, and debug checklist.
import-vocabulary
Imports a batch of Japanese vocabulary into the learning system from CSV or raw text.