nanoPyCodeAgent 0.1.0__tar.gz → 0.3.0__tar.gz

nanopycodeagent-0.3.0/.agents/skills/land-pr/SKILL.md

@@ -0,0 +1,85 @@
+---
+name: land-pr
+description: >
+  Use when merging a feature/bugfix PR into main — the everyday, no-release flow.
+  Makes the PR self-contained: rewrites the PR description from the PR's own
+  contents, appends a changelog [Unreleased] entry when warranted, regenerates the
+  English dev notes from the Chinese source when touched, and keeps the bilingual
+  README in sync. Then — only after explicit maintainer confirmation — merges the
+  PR. Does NOT tag or publish. Triggers on
+  "合并 PR / land PR / 合并这个 PR / merge this PR".
+---
+
+# Land a PR
+
+Merge a feature/bugfix PR into `main`, making the PR **self-contained** first:
+its code, changelog entry, dev notes (zh + en), and README (zh + en) all in sync
+within the PR. This skill never tags or publishes — that is the `release` skill's job.
+
+## Prerequisites
+
+`git` and `gh` (authenticated). See `docs/RELEASING.md`.
+
+## Steps
+
+Work on the PR's feature branch (not `main`). `<series>` is the current series
+file, e.g. `docs/changelogs/0.1.x.md` / `docs/dev_notes/{zh-CN,en}/0.1.x.md`.
+
+### 1. Preflight — stop if any check fails
+- `command -v git gh` — present.
+- `gh auth status` — authenticated.
+- `git status --porcelain` — empty (clean tree).
+- current branch is **not** `main` (`git branch --show-current`).
+
+### 2. Ensure a PR exists
+```bash
+gh pr view --json number,url 2>/dev/null || gh pr create --fill
+```
+Note the PR number for later steps.
+
+### 3. Append a changelog entry (when warranted)
+Inspect `git diff main...HEAD`. If the changes are worth recording for users, add
+an entry under `## [Unreleased]` in `<series>` (changelogs) in the right group
+(Added / Changed / Fixed / Removed). Purely internal/tooling changes may need
+**no** entry — decide, and surface the decision at the gate.
+
+### 4. Sync English dev notes (if the Chinese source changed)
+If this PR modified `docs/dev_notes/zh-CN/<series>.md`, regenerate the whole
+`docs/dev_notes/en/<series>.md` by translating the Chinese source. The English
+file is generated — do not hand-edit beyond this regeneration.
+
+### 5. Keep the bilingual README in sync
+If this PR changed only one of `README.md` / `README.zh-CN.md`, mirror the change
+into the other (translate/align) so the pair stays consistent. Both READMEs are
+hand-written sources — propose the synced change and let the maintainer adjust the
+wording at the gate; do not blindly overwrite. If both were already changed, skip.
+
+### 6. Commit and push the sync changes
+Commit any changes from steps 3–5 to the feature branch and push:
+```bash
+git commit -am "docs: sync changelog/dev-notes/README for this PR"
+git push
+```
+(Skip if steps 3–5 produced no changes.)
+
+### 7. Rewrite the PR description from scratch
+Build the description **only** from the PR's actual contents — commits, changed
+files, `gh pr diff`. **Do not read or extend the old description** (it may be
+stale). Update via the GitHub API (`gh pr edit` can fail on deprecated Projects
+Classic):
+```bash
+gh api repos/{owner}/{repo}/pulls/{number} -X PATCH -f body="..." --silent
+```
+
+### 8. ⛔ Confirmation gate (mandatory)
+Present to the maintainer: the rewritten **PR description**, the **changelog
+entry** added (or "none, because …"), and any **dev notes / README sync** done
+(or a README drift warning). **Wait for explicit confirmation** (e.g. "确认 / go").
+Do not merge until approved.
+
+### 9. Merge
+```bash
+gh pr merge --merge
+```
+Use the project's existing convention (merge commit; `--squash` only if asked).
+Done — do **not** tag or publish.

nanopycodeagent-0.3.0/.agents/skills/release/SKILL.md

@@ -0,0 +1,89 @@
+---
+name: release
+description: >
+  Use when cutting a new release of nanoPyCodeAgent (low-frequency). Does release
+  work only — assumes dev notes and README were already kept in sync per-PR by
+  land-pr. Picks the next version from the changelog [Unreleased], cuts the
+  changelog, then — only after explicit maintainer confirmation — commits the
+  changelog straight to main, pushes the vX.Y.Z tag (which triggers the PyPI +
+  GitHub Release CI), and verifies the published artifacts via uvx. Triggers on
+  "发布 / 发版 / cut a release / publish a release / 打 tag 发版".
+---
+
+# Release
+
+Cut and publish a new release of **nanoPyCodeAgent**. This skill does release
+work only; per-PR docs (dev notes, README) are kept in sync by the `land-pr`
+skill, not here.
+
+The version is derived from the git tag by `hatch-vcs` — **the tag is the source
+of truth**. Pushing a `v*` tag triggers `.github/workflows/release.yml`
+(`build` → `publish-to-pypi` → `github-release`).
+
+## Prerequisites
+
+`git`, `gh` (authenticated), and `uv` installed. See `docs/RELEASING.md`.
+
+## Steps
+
+Work entirely on `main`. `<series>` is the current series changelog file,
+e.g. `docs/changelogs/0.1.x.md`.
+
+### 1. Preflight — stop if any check fails
+- `command -v git gh uv` — all present.
+- `gh auth status` — authenticated.
+- `git status --porcelain` — empty (clean tree).
+- `<series>` has entries under `## [Unreleased]`. If empty, there is nothing to
+  release — stop.
+
+### 2. Switch to main and update
+```bash
+git checkout main && git pull --ff-only
+```
+
+### 3. Decide the version
+Read the entries under `## [Unreleased]` and propose the next semver `X.Y.Z`:
+- a `Removed`/breaking entry → major
+- an `Added` entry → minor
+- only `Fixed` → patch
+
+**0.x caveat:** on `0.y.z` a minor may still contain breaking changes; treat the
+proposal as a suggestion. The maintainer makes the final call at the gate (step 5).
+
+### 4. Cut the changelog
+In `<series>`:
+- rename `## [Unreleased]` to `## [X.Y.Z] - <today YYYY-MM-DD>`, keeping its entries;
+- add a fresh empty `## [Unreleased]` section above it.
+
+Touch no other file — dev notes and README were synced per-PR by `land-pr`.
+
+### 5. ⛔ Confirmation gate (mandatory)
+Present to the maintainer: the proposed **version** `X.Y.Z` and the **changelog
+diff** (`git diff <series>`). **Wait for explicit confirmation** (e.g. "确认 / go").
+Do not commit, push, or tag until approved. If the version changes, redo step 4.
+
+### 6. Commit and push to main
+```bash
+git commit -am "Release vX.Y.Z"
+git push origin main
+```
+
+### 7. Tag and push (triggers the release workflow)
+```bash
+git tag vX.Y.Z
+git push origin vX.Y.Z
+```
+
+### 8. Watch the release workflow
+```bash
+gh run watch
+```
+Confirm `build` → `publish-to-pypi` → `github-release` succeed. Publish steps are
+idempotent (`--check-url`, `gh release view || create`); a failed run is safe to re-run.
+
+### 9. Verify and report
+```bash
+.agents/skills/release/scripts/verify-release.sh vX.Y.Z
+```
+Polls official PyPI for the version, checks the GitHub Release has wheel + sdist,
+and runs a `uvx` smoke test. Report success, or surface the failure verbatim.

nanopycodeagent-0.3.0/.agents/skills/release/scripts/verify-release.sh

@@ -0,0 +1,71 @@
+#!/usr/bin/env bash
+# verify-release.sh — verify a published nanoPyCodeAgent release.
+#
+# Against the OFFICIAL PyPI index (bypassing any local mirror lag) it checks:
+#   1. the version is present on PyPI
+#   2. a GitHub Release exists for the tag with wheel + sdist assets
+#   3. `uvx ...@VERSION` runs the console entry point (smoke test)
+#
+# Usage: verify-release.sh <version|vVERSION>   e.g. verify-release.sh 0.1.1
+#
+# Smoke test runs the entry point with no args (currently side-effect-free).
+# If the entry point ever gains required args/interaction, adjust step 3.
+set -euo pipefail
+
+PACKAGE="nanoPyCodeAgent"
+PYPI_JSON="https://pypi.org/pypi/${PACKAGE}/json"
+PYPI_INDEX="https://pypi.org/simple/"
+POLL_TIMEOUT="${VERIFY_TIMEOUT:-300}"   # seconds budget per polling stage
+POLL_INTERVAL="${VERIFY_INTERVAL:-15}"  # seconds between polls
+
+usage() {
+  cat <<'EOF'
+Usage: verify-release.sh <version|vVERSION>
+
+Verifies a published release against official PyPI + GitHub Release:
+  1. version present on PyPI (pinned to pypi.org, ignores mirrors)
+  2. GitHub Release for the tag has wheel + sdist assets
+  3. uvx smoke test runs the published artifact
+
+Env overrides:
+  VERIFY_TIMEOUT   seconds to wait per polling stage (default 300)
+  VERIFY_INTERVAL  seconds between polls (default 15)
+EOF
+}
+
+if [[ $# -ne 1 ]]; then usage; exit 1; fi
+if [[ "$1" == "-h" || "$1" == "--help" ]]; then usage; exit 0; fi
+
+version="${1#v}"     # strip leading v -> 0.1.1
+tag="v${version}"    # normalized tag -> v0.1.1
+
+log()  { printf '\n=== %s ===\n' "$*"; }
+fail() { printf 'ERROR: %s\n' "$*" >&2; exit 1; }
+
+# 1. PyPI presence (poll, pinned to official index) -----------------------
+log "Checking PyPI for ${PACKAGE} ${version}"
+deadline=$(( $(date +%s) + POLL_TIMEOUT ))
+until curl -fsSL "$PYPI_JSON" | grep -q "\"${version}\""; do
+  (( $(date +%s) >= deadline )) && fail "version ${version} not on PyPI after ${POLL_TIMEOUT}s"
+  printf 'not on PyPI yet; retrying in %ss...\n' "$POLL_INTERVAL"; sleep "$POLL_INTERVAL"
+done
+printf 'OK: %s %s is on PyPI\n' "$PACKAGE" "$version"
+
+# 2. GitHub Release + assets ----------------------------------------------
+log "Checking GitHub Release ${tag}"
+gh release view "$tag" >/dev/null 2>&1 || fail "no GitHub Release for ${tag}"
+assets="$(gh release view "$tag" --json assets --jq '.assets[].name')"
+grep -q '\.whl$'     <<<"$assets" || fail "Release ${tag} missing a wheel (.whl) asset"
+grep -q '\.tar\.gz$' <<<"$assets" || fail "Release ${tag} missing an sdist (.tar.gz) asset"
+printf 'OK: GitHub Release %s has wheel + sdist\n' "$tag"
+
+# 3. uvx smoke test (official index, with retries) ------------------------
+log "Smoke-testing uvx ${PACKAGE}@${version}"
+deadline=$(( $(date +%s) + POLL_TIMEOUT ))
+until uvx --index "$PYPI_INDEX" --from "${PACKAGE}@${version}" "$PACKAGE" >/dev/null 2>&1; do
+  (( $(date +%s) >= deadline )) && fail "uvx smoke test failed for ${PACKAGE}@${version} after ${POLL_TIMEOUT}s"
+  printf 'uvx not ready (index propagation?); retrying in %ss...\n' "$POLL_INTERVAL"; sleep "$POLL_INTERVAL"
+done
+printf 'OK: uvx smoke test passed for %s@%s\n' "$PACKAGE" "$version"
+
+log "Release ${tag} verified ✔"

{nanopycodeagent-0.1.0 → nanopycodeagent-0.3.0}/.github/workflows/release.yml

@@ -33,7 +33,7 @@ jobs:
       - name: Check distribution metadata
         run: uvx twine check dist/*
       - name: Upload artifacts
-        uses: actions/upload-artifact@v4
+        uses: actions/upload-artifact@v7
         with:
           name: dist
           path: dist/
@@ -46,12 +46,16 @@ jobs:
       id-token: write # required for Trusted Publishing (OIDC)
     steps:
       - name: Download artifacts
-        uses: actions/download-artifact@v4
+        uses: actions/download-artifact@v8
         with:
           name: dist
           path: dist/
       - name: Install uv
         uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
+        with:
+          # No checkout in this job, so the cache-dependency glob (pyproject.toml,
+          # uv.lock) matches nothing; uv publish needs no resolved-dep cache anyway.
+          enable-cache: false
       - name: Publish to PyPI
         # --check-url makes re-runs idempotent: files already on the index are
         # skipped instead of failing the job on "file already exists".
@@ -65,7 +69,7 @@ jobs:
       contents: write # required to create the release and upload assets
     steps:
       - name: Download artifacts
-        uses: actions/download-artifact@v4
+        uses: actions/download-artifact@v8
         with:
           name: dist
           path: dist/

nanopycodeagent-0.3.0/AGENTS.md

@@ -0,0 +1,73 @@
+# AGENTS.md
+
+nanoPyCodeAgent — a nano code agent built from scratch in pure Python.
+
+This is the shared project instruction file for coding agents. Codex reads
+`AGENTS.md`; Claude Code reads `CLAUDE.md`, a symlink to this file.
+
+## Skills
+
+Project skills live in `.agents/skills/` and are auto-discovered by Codex and pi
+(`.agents/skills/**/SKILL.md`); Claude Code discovers them via `.claude/skills`
+(a symlink to `.agents/skills`). Use a skill by stating intent — the agent loads
+the matching one:
+
+- **Landing a PR** (everyday, no release) — merge a feature/bugfix PR into `main`:
+  `.agents/skills/land-pr/SKILL.md`
+- **Releasing** (cut a version, publish to PyPI + GitHub):
+  `.agents/skills/release/SKILL.md`
+
+See `docs/RELEASING.md` for the release process and prerequisites.
+
+## Language
+
+Write everything in **English** by default — source code (identifiers,
+comments, string literals), commit messages, PR titles/descriptions, changelog
+entries, and Markdown documentation.
+
+The **only** exception is documentation explicitly designated as Chinese:
+
+- `README.zh-CN.md` and any other `*.zh-CN.*` file.
+- Files under a `zh-CN/` directory (e.g. `docs/dev_notes/zh-CN/`).
+- Design specs under `docs/superpowers/specs/` — the prose may be Chinese for
+  review convenience, but the deliverables the spec produces (code under
+  `src/`, tests, and any English documentation) remain English.
+- Any document with an explicit requirement to be written in Chinese.
+
+Everything outside that list — including code under `src/`, this file, and all
+other docs — is English.
+
+## Commits & PRs
+
+All agents working in this repo MUST follow
+[Conventional Commits 1.0.0](https://www.conventionalcommits.org/en/v1.0.0/)
+for **commit messages** and **PR titles** (squash-merge often uses the PR
+title as the commit subject).
+
+**Format:**
+
+```
+<type>[optional scope][!]: <description>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+**Allowed types:** `feat`, `fix`, `docs`, `style`, `refactor`, `perf`,
+`test`, `build`, `ci`, `chore`, `revert`.
+
+**Rules:**
+
+- Description: imperative mood, lowercase, no trailing period.
+- Breaking changes: add `!` after the type/scope and/or include a
+  `BREAKING CHANGE:` footer.
+- Separate the optional body and footer(s) from the description with a
+  blank line.
+
+**Examples:**
+
+- `feat: add streaming output to the agent loop`
+- `fix(parser): handle empty tool-call arguments`
+- `docs: require Conventional Commits in AGENTS.md`
+- `refactor!: drop Python 3.9 support` (breaking change)

nanopycodeagent-0.3.0/CLAUDE.md

@@ -0,0 +1 @@
+AGENTS.md

{nanopycodeagent-0.1.0 → nanopycodeagent-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nanoPyCodeAgent
-Version: 0.1.0
+Version: 0.3.0
 Summary: A nano code agent built from scratch in pure Python.
 Project-URL: Homepage, https://github.com/minixalpha/nanoPyCodeAgent
 Project-URL: Repository, https://github.com/minixalpha/nanoPyCodeAgent
@@ -13,6 +13,7 @@ Classifier: Intended Audience :: Developers
 Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3.13
 Requires-Python: >=3.13
+Requires-Dist: anthropic>=0.112.0
 Description-Content-Type: text/markdown
 
 # nanoPyCodeAgent
@@ -60,6 +61,32 @@ uvx --from "git+https://github.com/minixalpha/nanoPyCodeAgent@main" nanoPyCodeAg
 uvx --from "git+https://github.com/minixalpha/nanoPyCodeAgent@v0.1.0" nanoPyCodeAgent
 ```
 
+### Configuration
+
+Credentials and the model come from two sources: **environment variables** and
+an optional user-level config file at `~/.nanoPyCodeAgent/settings.json`.
+Environment variables take precedence — the config file only fills in keys you
+have not set in the environment.
+
+The config file mirrors [Claude Code's settings](https://code.claude.com/docs/en/settings):
+put the values under an `env` object. Empty or whitespace-only values are ignored.
+
+```json
+{
+  "env": {
+    "ANTHROPIC_API_KEY": "",
+    "ANTHROPIC_BASE_URL": "",
+    "ANTHROPIC_MODEL": ""
+  }
+}
+```
+
+| Variable | Required | Default | Description |
+| --- | --- | --- | --- |
+| `ANTHROPIC_API_KEY` | Yes | — | Your Anthropic API key, or the key for a third-party / proxy service. |
+| `ANTHROPIC_BASE_URL` | No | `https://api.anthropic.com` | Point the SDK at a non-official / proxy endpoint. Leave it unset to use the official API — an empty value breaks requests. |
+| `ANTHROPIC_MODEL` | No | `claude-sonnet-4-6` | Override the model. An empty or whitespace-only value falls back to the default. |
+
 ### How to Update
 
 Upgrade an installed tool to the latest release:
@@ -67,3 +94,7 @@ Upgrade an installed tool to the latest release:
 ```bash
 uv tool upgrade nanoPyCodeAgent   # or: pipx upgrade nanoPyCodeAgent
 ```
+
+## Releasing
+
+For maintainers: see [docs/RELEASING.md](docs/RELEASING.md) for the release process and prerequisites.

nanopycodeagent-0.3.0/README.md

@@ -0,0 +1,82 @@
+# nanoPyCodeAgent
+
+[English](README.md) | [简体中文](README.zh-CN.md)
+
+A nano code agent built in pure Python.
+
+> "What I cannot create, I do not understand." — Richard Feynman, 1988
+
+## Usage
+
+nanoPyCodeAgent requires Python 3.13 or newer.
+
+### How to Run
+
+There are a few ways to run it — pick whichever fits your workflow.
+
+#### Run without installing
+
+Use `uvx` to run the latest release without installing anything:
+
+```bash
+uvx nanoPyCodeAgent
+```
+
+#### Run after installing
+
+Install it as a persistent command-line tool, then run it from anywhere:
+
+```bash
+uv tool install nanoPyCodeAgent   # or: pipx install nanoPyCodeAgent
+nanoPyCodeAgent
+```
+
+#### Run a branch or tagged version
+
+Run an unreleased branch or a specific release tag straight from GitHub:
+
+```bash
+# latest commit on a branch
+uvx --from "git+https://github.com/minixalpha/nanoPyCodeAgent@main" nanoPyCodeAgent
+
+# a specific tag
+uvx --from "git+https://github.com/minixalpha/nanoPyCodeAgent@v0.1.0" nanoPyCodeAgent
+```
+
+### Configuration
+
+Credentials and the model come from two sources: **environment variables** and
+an optional user-level config file at `~/.nanoPyCodeAgent/settings.json`.
+Environment variables take precedence — the config file only fills in keys you
+have not set in the environment.
+
+The config file mirrors [Claude Code's settings](https://code.claude.com/docs/en/settings):
+put the values under an `env` object. Empty or whitespace-only values are ignored.
+
+```json
+{
+  "env": {
+    "ANTHROPIC_API_KEY": "",
+    "ANTHROPIC_BASE_URL": "",
+    "ANTHROPIC_MODEL": ""
+  }
+}
+```
+
+| Variable | Required | Default | Description |
+| --- | --- | --- | --- |
+| `ANTHROPIC_API_KEY` | Yes | — | Your Anthropic API key, or the key for a third-party / proxy service. |
+| `ANTHROPIC_BASE_URL` | No | `https://api.anthropic.com` | Point the SDK at a non-official / proxy endpoint. Leave it unset to use the official API — an empty value breaks requests. |
+| `ANTHROPIC_MODEL` | No | `claude-sonnet-4-6` | Override the model. An empty or whitespace-only value falls back to the default. |
+
+### How to Update
+
+Upgrade an installed tool to the latest release:
+
+```bash
+uv tool upgrade nanoPyCodeAgent   # or: pipx upgrade nanoPyCodeAgent
+```
+
+## Releasing
+
+For maintainers: see [docs/RELEASING.md](docs/RELEASING.md) for the release process and prerequisites.

{nanopycodeagent-0.1.0 → nanopycodeagent-0.3.0}/README.zh-CN.md

@@ -43,6 +43,31 @@ uvx --from "git+https://github.com/minixalpha/nanoPyCodeAgent@main" nanoPyCodeAg
 uvx --from "git+https://github.com/minixalpha/nanoPyCodeAgent@v0.1.0" nanoPyCodeAgent
 ```
 
+### 配置
+
+凭据与模型有两种配置来源:**环境变量**,以及可选的用户级配置文件
+`~/.nanoPyCodeAgent/settings.json`。环境变量优先级更高——配置文件只用于填补你
+未在环境变量中设置的键。
+
+配置文件写法与 [Claude Code settings](https://code.claude.com/docs/en/settings)
+一致:把值放在 `env` 对象下。空值或纯空白会被忽略。
+
+```json
+{
+  "env": {
+    "ANTHROPIC_API_KEY": "",
+    "ANTHROPIC_BASE_URL": "",
+    "ANTHROPIC_MODEL": ""
+  }
+}
+```
+
+| 变量 | 是否必填 | 默认值 | 说明 |
+| --- | --- | --- | --- |
+| `ANTHROPIC_API_KEY` | 是 | 无 | 你的 Anthropic API key,或第三方/代理服务的 key。 |
+| `ANTHROPIC_BASE_URL` | 否 | `https://api.anthropic.com` | 将 SDK 指向非官方/代理 endpoint。使用官方 API 时保持不设置;留空值会导致请求失败。 |
+| `ANTHROPIC_MODEL` | 否 | `claude-sonnet-4-6` | 覆盖默认模型。空值或纯空白会回退到默认值。 |
+
 ### 如何更新
 
 将已安装的工具升级到最新发布版:
@@ -50,3 +75,7 @@ uvx --from "git+https://github.com/minixalpha/nanoPyCodeAgent@v0.1.0" nanoPyCode
 ```bash
 uv tool upgrade nanoPyCodeAgent   # 或: pipx upgrade nanoPyCodeAgent
 ```
+
+## 发布
+
+维护者请参阅 [docs/RELEASING.md](docs/RELEASING.md) 了解发布流程与前置条件。

nanopycodeagent-0.3.0/docs/RELEASING.md

@@ -0,0 +1,33 @@
+# Releasing
+
+How nanoPyCodeAgent is maintained and released. Two agent skills drive the flow;
+this document is the human reference.
+
+## Prerequisites (maintainers)
+
+- **`uv`** — build / publish / run (`uvx`).
+- **`gh`** — GitHub CLI, authenticated (`gh auth status`).
+- **`git`**.
+- One-time: PyPI Trusted Publishing must be configured for this repo (see the
+  header comment in `.github/workflows/release.yml`).
+
+## Two skills
+
+| Skill | When | What it does | Publishes? |
+|-------|------|--------------|------------|
+| `land-pr` | Every feature/bugfix PR | Rewrites the PR description, appends a changelog `[Unreleased]` entry when warranted, syncs dev notes (zh→en) and the bilingual README, then merges after confirmation. | No |
+| `release` | Cutting a version | Picks the next version from `[Unreleased]`, cuts the changelog, commits to `main`, pushes the `vX.Y.Z` tag (triggering CI), and verifies PyPI + GitHub Release. | Yes |
+
+The changelog flows across both: `land-pr` accumulates entries under
+`[Unreleased]`; `release` turns `[Unreleased]` into a dated version section.
+
+## How it publishes
+
+Pushing a `v*` tag triggers `.github/workflows/release.yml`:
+`build` → `publish-to-pypi` (PyPI Trusted Publishing / OIDC) → `github-release`.
+The version is derived from the git tag by `hatch-vcs`.
+
+## Triggering the skills
+
+State intent to your agent — "land this PR" / "合并 PR", or "cut a release" /
+"发布". The agent loads the matching skill from `.agents/skills/`.

nanopycodeagent-0.3.0/docs/changelogs/0.1.x.md

@@ -0,0 +1,32 @@
+# Changelog — 0.1.x
+
+All notable changes in the **0.1.x** release series are documented here.
+
+## [Unreleased]
+
+### Added
+- Project-level agent skills `land-pr` and `release` (in `.agents/skills/`, cross-agent: Claude Code / Codex / pi), with a `verify-release.sh` post-publish check, a root `AGENTS.md`, and `docs/RELEASING.md`.
+- Contributing convention: all agents must follow Conventional Commits 1.0.0 for commit messages and PR titles (documented in `AGENTS.md`).
+
+### Changed
+- CI: upgrade the release workflow's artifact actions off the deprecated Node 20 runtime — `actions/upload-artifact` v4 → v7 and `actions/download-artifact` v4 → v8 — and disable the unused `setup-uv` cache in the `publish-to-pypi` job, which has no checkout so its cache-dependency glob matched nothing (#3).
+
+## [0.1.0] - 2026-06-20
+
+### Added
+- uv-managed project with the console-script entry point `nanoPyCodeAgent`.
+- Tag-driven release pipeline: PyPI Trusted Publishing + GitHub Release.
+- Bilingual README (English / 简体中文).
+- changelogs and dev notes
+
+<!--
+When cutting a release, copy the relevant items from [Unreleased] into a new
+version section above it, e.g.:
+
+## [0.1.1] - YYYY-MM-DD
+
+### Added
+### Changed
+### Fixed
+### Removed
+-->

nanopycodeagent-0.3.0/docs/changelogs/0.2.x.md

@@ -0,0 +1,23 @@
+# Changelog — 0.2.x
+
+All notable changes in the **0.2.x** release series are documented here.
+
+## [Unreleased]
+
+## [0.2.0] - 2026-07-09
+
+### Added
+- Interactive agent loop: a multi-turn chatbot built on the Anthropic Python SDK that keeps the full conversation in memory for context and quits on `/exit`.
+- Configurable endpoint, API key, and model via environment variables (`ANTHROPIC_API_KEY` / `ANTHROPIC_BASE_URL` / `ANTHROPIC_MODEL`) and an optional user-level config file `~/.nanoPyCodeAgent/settings.json`, whose `env` object mirrors [Claude Code's settings](https://code.claude.com/docs/en/settings). Environment variables take precedence; only `ANTHROPIC_*` keys are read, and empty / whitespace-only values are ignored. A missing, unreadable, or malformed config file never blocks startup, and Ctrl-C quits cleanly.
+
+<!--
+When cutting a release, copy the relevant items from [Unreleased] into a new
+version section above it, e.g.:
+
+## [0.2.0] - YYYY-MM-DD
+
+### Added
+### Changed
+### Fixed
+### Removed
+-->

nanopycodeagent-0.3.0/docs/changelogs/0.3.x.md

@@ -0,0 +1,22 @@
+# Changelog — 0.3.x
+
+All notable changes in the **0.3.x** release series are documented here.
+
+## [Unreleased]
+
+## [0.3.0] - 2026-07-10
+
+### Changed
+- Agent replies now stream to the terminal as they are generated, instead of appearing all at once after the full response is ready.
+
+<!--
+When cutting a release, copy the relevant items from [Unreleased] into a new
+version section above it, e.g.:
+
+## [0.3.0] - YYYY-MM-DD
+
+### Added
+### Changed
+### Fixed
+### Removed
+-->

nanopycodeagent-0.3.0/docs/dev_notes/en/0.2.x.md

@@ -0,0 +1,24 @@
+# Development Notes — 0.2.x
+
+> Generated from the Chinese source [`../zh-CN/0.2.x.md`](../zh-CN/0.2.x.md). Do not edit by hand.
+
+## 0.2.0 - 2026.06.29
+
+This release implements a minimally functional chatbot that holds a multi-turn conversation with the LLM through the [Messages](https://platform.claude.com/docs/en/api/python/messages/create) API.
+
+The LLM's endpoint, key, and model can be configured in two ways:
+
+- **Environment variables**: the variable names follow [Claude Code's environment variables](https://code.claude.com/docs/en/env-vars); the three common ones are `ANTHROPIC_API_KEY`, `ANTHROPIC_BASE_URL`, and `ANTHROPIC_MODEL`.
+- **Config file**: located at `~/.nanoPyCodeAgent/settings.json`, with values placed under its `env` field, using the same convention as the `env` field in [Claude Code's settings](https://code.claude.com/docs/en/settings). Example:
+
+  ```json
+  {
+    "env": {
+      "ANTHROPIC_API_KEY": "",
+      "ANTHROPIC_BASE_URL": "",
+      "ANTHROPIC_MODEL": ""
+    }
+  }
+  ```
+
+The two can be mixed, and **environment variables take precedence over the config file**: when a key is already set in the environment, the config file's value for that same key is ignored; the config file only fills in keys the environment leaves unset. The empty strings in the example are placeholders — empty values (empty or whitespace-only) are skipped.