MacHu-GWU/sqlalchemy_upsert_kit-project / .claude/skills/pywf-oss-setup-repo
pywf-oss-setup-repo
VerifiedTake a freshly generated pywf open-source Python library repo live: verify it locally, create and push the GitHub repo, set its metadata, connect Codecov and Read the Docs, enable CI, and confirm all are green, with the user's yes before each external step. Use when the user has a new repo from the template and wants it on GitHub with CI, coverage, and hosted docs.
Turn a local repo generated from the template into a live project, with GitHub, CI, Codecov, and Read the Docs all green. Each external step waits for the user's yes; one yes covers one step.
Read ../pywf-oss-base/SKILL.md, then:
- ../pywf-oss-base/references/01-secrets.md
- ../pywf-oss-base/references/03-mise.md
- ../pywf-oss-base/references/19-github-actions.md
- ../pywf-oss-base/references/20-codecov.md
- ../pywf-oss-base/references/21-readthedocs.md
Steps
- Preflight.
- Run the token True/False check. If any token is
False, stop and hand off topywf-oss-setup-machine. - Read
[project].namefrompyproject.toml, and rungit remote -v. - No
originyet: propose the GitHub owner and the repo name<package_name>-project, and wait for the user to confirm. Step 3 creates the repo and remote. originexists: show the GitHub repo URL, the Read the Docs slug, and the docs URL the tasks will use (.mise/tasks/utils.pyderives them fromoriginand the project name), and ask the user to confirm.
- Run the token True/False check. If any token is
- Local green.
mise run inst,mise run cov,mise run lint, andmise run build-docpass; template-fresh code should. Fix any failure before going online. - GitHub repo. If none exists, propose
gh repo create <owner>/<repo> --public --source . --remote origin --push, and run it after the user's yes. Then show the URL, slug, and docs URL derived from the neworigin. - GitHub metadata.
mise run update-github-metadata, after the user's yes. - Codecov.
mise run setup-codecov, after the user's yes. Confirm the secret withgh secret list(names only). - Read the Docs.
mise run setup-readthedocs, after the user's yes. - CI. Show the change that enables the
pushandpull_requesttriggers in.github/workflows/main.yml, commit and push it after the user's yes, and watch the run withgh run listandgh run view. - Confirm. Report the CI run, the Codecov project, and the docs build as green or red. Diagnose anything red with
19-github-actions.md,20-codecov.md, or21-readthedocs.md, or hand off topywf-oss-fix-ci.
Boundaries
- Never change repo visibility, branch protection, or any repo setting not listed in these steps.
Next steps: pywf-oss-add-module to start coding, pywf-oss-release for the first version, and pywf-oss-write-maintain-skill once there is something to say about maintaining it.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |