Skip to content
Skills Library
Programming · Building & coding

contributing-changes

/contributing-changes

Use when preparing a change for the tycoon-cli repo: choosing which branch to target, opening a PR, updating the changelog, or when CI behaves differently than expected because workflow config differs between main and the release branch.

Repository
tycoon-cli ↗
Licence
MIT
Last repository change
24.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when preparing a change for the tycoon-cli repo: choosing which branch to target, opening a PR, updating the changelog, or when CI behaves differently than expected because workflow config differs between main and the release branch.

Original author description

Use when preparing a change for the tycoon-cli repo: choosing which branch to target, opening a PR, updating the changelog, or when CI behaves differently than expected because workflow config differs between main and the release branch.

How it works

  1. Which branch to target
  2. Change checklist
  3. Code conventions
Original SKILL.md headings · 48 lines, 344 words
SKILL.md preview
---
name: contributing-changes
description: Use when preparing a change for the tycoon-cli repo: choosing which branch to target, opening a PR, updating the changelog, or when CI behaves differently than expected because workflow config differs between main and the release branch.
license: MIT
compatibility: tycoon-cli repository checkout with uv
metadata:
  author: database-tycoon
  tier: contributors
---

# Contributing changes

CONTRIBUTING.md is the authority for PR size, titles, issue links, the
Mental model section and the release process. This skill covers what an agent
most often gets wrong, and points at the section that settles each one.

## Which branch to target

Target the **active release branch**, never `main`. `main` only advances when a
finished release branch merges into it. CONTRIBUTING.md, "Release process"
and "Merging into the release branch" say how a branch
becomes active and how it merges.

Do not guess from branch names. Old release branches are never deleted, so the
set of open version branches includes abandoned ones. To find the active
branch, read the base of the most recently merged PR, or ask in the issue.

Consequences:

- CI workflow config and tool pins live on the release branch and may differ
  from `main`. Diagnose a PR's check failures against the release branch's
  `.github/workflows/`, not `main`'s.
- A regression test should fail on the release branch and pass on yours.

## Change checklist

1. Open an issue first for anything non-trivial (CONTRIBUTING.md, "Break up
   large issues").
2. Branch from the active release branch.
3. Tests: new behaviour needs a test, and a bug fix needs a regression test. For
   a CLI-surface bug, use the subprocess layer (testing-cli-changes skill).
4. Update `CHANGELOG.md` under `[Unreleased]` in the section for the change's
   type.
5. A user-visible change also updates `README.md` and the relevant `docs/` page.
6. Before pushing, run the gates CI runs, with `uv run`:
   `uv run pytest -q`, `uv run ruff check src tests`,
   `uv run ruff format --check src tests`. Do not use `uvx ruff`: it resolves
   the latest release, not the version CI pins (CONTRIBUTING.md, "What CI gates on").
7. Open the PR as a draft, with the template body and a Mental model section.

## Code conventions

CONTRIBUTING.md, "Code conventions", is authoritative. The rules
reviews repeat most: no comments that describe what code does (only a
non-obvious why), no unused imports or half-finished implementations, no
backwards-compatibility shims before 1.0, and one logical change per commit.

Versions

The database has no other skills named contributing-changes.

Database snapshot: 13.11.2026 · package version eef75ce91cce (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100contributing
    Guides a change to GridSelect from issue to pull request so it meets the project's standards (tests first, browser tests, accessibility, README and CHANGELOG, size budget, no version bumps). Use when contributing to this repository, fixing a bug, adding a feature or theme, or…
  • 100testing-cli-changes
    Use when writing or fixing tests in the tycoon-cli repo, when a CLI-surface bug slipped past in-process tests (PATH resolution, Rich rendering, console-script wiring, exit codes), when snapshot tests fail after changing user-facing strings, or when adding runnable bash examples…
  • 100cutting-a-release
    Use when cutting or publishing a tycoon release: opening the next version branch, finalizing CHANGELOG.md and docs/releases/, merging the release branch to main, pushing the version tag, or troubleshooting the PyPI trusted-publishing workflow.
  • 100hk-changelog
    Write a CHANGELOG.md entry from the branch's diff against main, then commit it on a changelog branch and open a PR. Triggers on: 'update the changelog', 'changelog entry', 'add to the changelog', or /hk-changelog.
  • 100ac-release
    Release workflow: branch, changelog, PR, tag, GH release. Triggers on keywords: release, create release, publish release, tag release
  • 86pr
    Use for /pr, or ''create a PR'' / ''open a pull request'' — creates a pull request for the current branch against the repo''s base branch with a formatted title and body. Not for reviewing an existing PR (review-pr).

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.