Rename skill from pyckage to python-package-development

- Skill name: python-package-development (descriptive, follows posit-dev convention)
- Future PyPI package will be: packright (separate repo)
- GitHub repo renamed: Naareman/python-package-development
- Updated all /pyckage references to /python-package-development
- Updated README with new install/usage instructions
- Added link to future packright companion package

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Naareman

README.md

@@ -1,57 +1,55 @@
-# pyckage
+# python-package-development
 
-> *"Just as Hadley Wickham brought the Grammar of Graphics to R as ggplot2, pyckage brings the philosophy of R package development to Python."*
+> *"Just as Hadley Wickham brought the Grammar of Graphics to R as ggplot2, this skill brings the philosophy of R package development to Python."*
 
-## What is pyckage?
+## What is this?
 
-**pyckage** is a [Claude Code](https://docs.anthropic.com/en/docs/claude-code) skill that teaches Claude how to build Python packages the right way — using the hard-won wisdom of the R package ecosystem.
+**python-package-development** is a [Claude Code](https://docs.anthropic.com/en/docs/claude-code) skill that teaches Claude how to build Python packages the right way — using the hard-won wisdom of the R package ecosystem.
 
 Python has incredible packages. But it has never had a unified philosophy for *building* them. The R world has one: Hadley Wickham's [*R Packages*](https://r-pkgs.org/) book (with Jenny Bryan), backed by tools like `devtools`, `usethis`, `roxygen2`, `cli`, and `lifecycle`.
 
-pyckage translates that philosophy into Python using modern tools: `uv`, `rich`, `pytest`, and `mkdocs-material`.
+This skill translates that philosophy into Python using modern tools: `uv`, `rich`, `pytest`, and `mkdocs-material`.
+
+> Looking for the CLI tool? See [packright](https://github.com/Naareman/packright) — the companion Python package that automates these conventions from the command line.
 
 ## Installation
 
 ### For all your projects (personal scope)
 
 ```bash
-# Clone the repo
-git clone https://github.com/Naareman/pyckage.git
-
-# Copy to your Claude skills directory
-cp -r pyckage ~/.claude/skills/pyckage
+git clone https://github.com/Naareman/python-package-development.git
+cp -r python-package-development ~/.claude/skills/python-package-development
 ```
 
 ### For a single project (project scope)
 
 ```bash
-# From your project root
 mkdir -p .claude/skills
-cp -r /path/to/pyckage .claude/skills/pyckage
+cp -r /path/to/python-package-development .claude/skills/python-package-development
 ```
 
 ### Verify it's installed
 
-In Claude Code, run `/pyckage` — you should see it in the skill list.
+In Claude Code, run `/python-package-development` — you should see it in the skill list.
 
 ## Usage
 
-pyckage activates automatically when you're working on Python package tasks. You can also invoke it explicitly:
+The skill activates automatically when you're working on Python package tasks. You can also invoke it explicitly:
 
 ```
-/pyckage scaffold my-new-package    # Create a new package from scratch
-/pyckage api                        # Review and improve your API design
-/pyckage test                       # Set up or improve tests
-/pyckage docs                       # Set up mkdocs + docstrings
-/pyckage lifecycle                  # Manage deprecations and versioning
-/pyckage release                    # Walk through the PyPI release ritual
-/pyckage check                      # Audit your project for common mistakes
-/pyckage pre-commit                 # Set up pre-commit hooks
-/pyckage cli                        # Add a CLI to your package
-/pyckage                            # Assess your project against all 5 principles
+/python-package-development scaffold my-new-package
+/python-package-development api
+/python-package-development test
+/python-package-development docs
+/python-package-development lifecycle
+/python-package-development release
+/python-package-development check
+/python-package-development pre-commit
+/python-package-development cli
+/python-package-development
 ```
 
-Or just describe what you need — pyckage will activate when it recognizes a Python packaging task:
+Or just describe what you need — the skill activates when it recognizes a Python packaging task:
 
 - *"I want to make a Python library"*
 - *"Help me structure my code as a package"*
@@ -61,23 +59,23 @@ Or just describe what you need — pyckage will activate when it recognizes a Py
 ## The Philosophy (what R taught us)
 
 ### 1. User communication is a first-class concern
-R's `cli` package made it easy to produce beautiful, structured messages. **pyckage** brings this to Python through `rich` and structured exception hierarchies.
+R's `cli` package made beautiful, structured messages easy. This skill brings that to Python through `rich` and structured exception hierarchies.
 
 ### 2. Function names form a grammar
-Tidyverse packages use `verb_noun()` consistently. Users can *guess* function names because the grammar is predictable. **pyckage** encodes naming conventions that make your API feel intentional.
+Tidyverse packages use `verb_noun()` consistently. Users can *guess* function names because the grammar is predictable.
 
 ### 3. Lifecycle deserves ceremony
-R's `lifecycle` package gave deprecations a formal process. Users are never surprised. **pyckage** brings the same discipline to Python's `warnings` system.
+R's `lifecycle` package gave deprecations a formal process. Users are never surprised.
 
 ### 4. Documentation lives next to code
-`roxygen2` made it impossible to forget documentation. **pyckage** enforces Google-style docstrings + `mkdocstrings` so docs are always a byproduct of writing good code.
+`roxygen2` made it impossible to forget documentation. This skill enforces Google-style docstrings + `mkdocstrings`.
 
 ### 5. There is a whole game
-Before diving into details, you should be able to see the whole thing working end-to-end. **pyckage** gives you a complete, working package skeleton from the first command.
+Before diving into details, you should see the whole thing working end-to-end.
 
-## What pyckage Covers
+## What This Skill Covers
 
-| Stage | R equivalent | Python (pyckage) |
+| Stage | R equivalent | Python |
 |---|---|---|
 | Scaffold | `usethis::create_package()` | `uv init` + src layout |
 | Dependency management | `DESCRIPTION` + `devtools` | `pyproject.toml` + `uv` |
@@ -92,7 +90,7 @@ Before diving into details, you should be able to see the whole thing working en
 ## Skill Structure
 
 ```
-pyckage/
+python-package-development/
 ├── SKILL.md                          # Main skill definition (philosophy + routing)
 ├── README.md                         # This file
 ├── examples/
@@ -111,24 +109,22 @@ pyckage/
 │   └── 11-automated-release.md       # Automated version bumps + changelog
 ├── scripts/
 │   ├── count-tokens.py               # Token budget checker
-│   └── check-structure.py            # Audit project against pyckage conventions
+│   └── check-structure.py            # Audit project against conventions
 └── .github/
     └── workflows/
         └── check-budget.yml          # CI: token budget check on PRs
 ```
 
 ## Token Budget
 
-pyckage follows [posit-dev/skills](https://github.com/posit-dev/skills) conventions for skill size:
+Follows [posit-dev/skills](https://github.com/posit-dev/skills) (Posit, the company behind RStudio) conventions:
 
 - SKILL.md description: under 100 tokens
 - SKILL.md body: under 5,000 tokens / 500 lines
 - Reference files: loaded on demand (no hard limit)
 
-Check with:
 ```bash
 python3 scripts/count-tokens.py .
-# Install tiktoken for exact counts: pip install tiktoken
 ```
 
 ## Contributing

SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: pyckage
+name: python-package-development
 description: >
   Build Python packages the right way — R-inspired philosophy for scaffolding, API design,
   testing, docs, deprecation lifecycle, and PyPI release using uv, rich, pytest, and
@@ -9,7 +9,7 @@ description: >
 argument-hint: "[scaffold|api|test|docs|lifecycle|release|check|pre-commit|cli] [package-name]"
 ---
 
-# pyckage
+# python-package-development
 
 A skill for building Python packages with the philosophy of the R package ecosystem:
 clear user communication, principled API design, living documentation, and ceremonial lifecycle management.
@@ -103,22 +103,22 @@ Key decisions encoded here:
 
 ## Argument Routing
 
-When invoked with `/pyckage <subcommand>`, route based on the first argument:
+When invoked with `/python-package-development <subcommand>`, route based on the first argument:
 
 | Invocation | Action |
 |---|---|
-| `/pyckage scaffold <name>` | Read [references/01-scaffold.md](references/01-scaffold.md) and create a new package named `<name>` |
-| `/pyckage api` | Read [references/02-api-design.md](references/02-api-design.md) and review/improve the current package's API |
-| `/pyckage test` | Read [references/03-testing.md](references/03-testing.md) and set up or improve tests |
-| `/pyckage docs` | Read [references/04-docs.md](references/04-docs.md) and set up or improve documentation |
-| `/pyckage lifecycle` | Read [references/05-lifecycle.md](references/05-lifecycle.md) and manage deprecations |
-| `/pyckage release` | Read [references/06-release.md](references/06-release.md) and walk through the release ritual |
-| `/pyckage check` | Read [references/07-common-mistakes.md](references/07-common-mistakes.md) and audit current project for anti-patterns |
-| `/pyckage pre-commit` | Read [references/08-pre-commit.md](references/08-pre-commit.md) and set up pre-commit hooks |
-| `/pyckage cli` | Read [references/09-cli-entry-points.md](references/09-cli-entry-points.md) and add a CLI to the package |
-| `/pyckage` (no args) | Assess the current project against all five principles (see checklist below) |
-
-When invoked without a subcommand (auto-triggered or plain `/pyckage`), run this assessment:
+| `/python-package-development scaffold <name>` | Read [references/01-scaffold.md](references/01-scaffold.md) and create a new package named `<name>` |
+| `/python-package-development api` | Read [references/02-api-design.md](references/02-api-design.md) and review/improve the current package's API |
+| `/python-package-development test` | Read [references/03-testing.md](references/03-testing.md) and set up or improve tests |
+| `/python-package-development docs` | Read [references/04-docs.md](references/04-docs.md) and set up or improve documentation |
+| `/python-package-development lifecycle` | Read [references/05-lifecycle.md](references/05-lifecycle.md) and manage deprecations |
+| `/python-package-development release` | Read [references/06-release.md](references/06-release.md) and walk through the release ritual |
+| `/python-package-development check` | Read [references/07-common-mistakes.md](references/07-common-mistakes.md) and audit current project for anti-patterns |
+| `/python-package-development pre-commit` | Read [references/08-pre-commit.md](references/08-pre-commit.md) and set up pre-commit hooks |
+| `/python-package-development cli` | Read [references/09-cli-entry-points.md](references/09-cli-entry-points.md) and add a CLI to the package |
+| `/python-package-development` (no args) | Assess the current project against all five principles (see checklist below) |
+
+When invoked without a subcommand (auto-triggered or plain `/python-package-development`), run this assessment:
 
 1. **Structure** — Is there a `src/` layout? Does `__init__.py` have `__all__`?
 2. **Communication** — Is there an `errors.py` with a base exception? A `_messages.py` with `rich`?

scripts/count-tokens.py

@@ -105,7 +105,7 @@ def main() -> None:
         files.extend(sorted(scripts_dir.glob("*.py")))
 
     # Header
-    print(f"\n  pyckage token budget: {skill_name}")
+    print(f"\n  skill token budget: {skill_name}")
     print(f"  Method: {method}")
     print(f"  {'=' * 64}")