githits 0.20.0 → 0.21.0

package/skills/githits-code/references/code-and-docs.md

@@ -1,6 +1,6 @@
 # GitHits Code And Docs CLI Reference
 
-Package target syntax requires an explicit registry: `registry:name[@version]`, for example `npm:express@5.2.1`; omit `@version` for the latest release. Package targets inspect an indexed artifact/manifest root. Swift package targets use `swift:github.com/<owner>/<repo>` and Zig package targets use `zig:gh/<owner>/<repo>`. Use public repository targets for full repositories or sibling packages. Repository compact targets use `github:org/repo[@ref]`, `codeberg:owner/repo[@ref]`, `gitlab:group[/subgroup...]/project[@ref]`, `github.com/org/repo[@ref]`, or `https://github.com/org/repo[@ref]`; omitted refs request the backend default-branch intent. Exact standalone documentation sites use `site:<host[/path]>`. Output uses canonical `provider:path@ref` formatting so refs can contain `@` safely. `code` commands also support `--repo-url <url> [--git-ref <ref>]`.
+Package target syntax requires an explicit registry: `registry:name@version`, for example `npm:express@5.2.1`; omit `@version` for the latest release. Package targets scope to the package subpath, including within monorepos. Swift package targets use `swift:github.com/<owner>/<repo>` and Zig package targets use `zig:gh/<owner>/<repo>`. Use public repository targets for full repositories or sibling packages. Repository compact targets use `github:org/repo@ref`, `codeberg:owner/repo@ref`, `gitlab:group/subgroup/project@ref`, `github.com/org/repo@ref`, or `https://github.com/org/repo@ref`; omit `@ref` for the backend default branch. Exact standalone documentation sites use `site:<host[/path]>`. Output uses canonical `provider:path@ref` formatting so refs can contain `@` safely. `code` commands also support `--repo-url <url>` with optional `--git-ref <ref>`.
 
 ## Search
 

package/skills/githits-mcp/SKILL.md

@@ -26,21 +26,22 @@ This guide owns shared policy; selected tools own call syntax and exceptions.
 | Assess a package's license, adoption, maintenance, or overall health | `pkg_info` |
 | Inspect vulnerabilities in a package or version | `pkg_vulns` |
 | Inspect direct dependencies or transitive footprint | `pkg_deps` |
-| Find release notes for a package or repository | `pkg_changelog` |
+| Find release notes and changelog history for a package | `pkg_changelog` |
 | Compare current and target dependency versions for an upgrade | `pkg_upgrade_review` |
 | Find canonical implementation examples across projects | `get_example` |
 | Check progress of an earlier search reference | `search_status` |
 
 For comparisons, combine relevant package/source evidence with examples as needed.
 
-Public OSS only; never send local/private/proprietary source. Packages use
-`registry:name[@version]` for an indexed artifact/manifest root; Swift uses
+Public OSS only; never send local/private/proprietary source. Package/repository
+patterns are `registry:name@version` and `github:owner/repo@ref`. Omit the
+suffix for the latest package version or repository default branch. Package
+targets scope to the package subpath, including in monorepos. Swift uses
 `swift:github.com/<owner>/<repo>`, Zig `zig:gh/<owner>/<repo>`.
 Use public repository targets for full repositories or sibling packages:
 `github:`, `codeberg:`, `gitlab:`, or a supported full URL. Never infer a provider.
-Revisions use `@ref` and may contain later `@` characters; `#` is reserved
-for semantic fragments, not revisions. Selected tools state supported forms
-and pin/ref restrictions.
+A ref may be a branch, tag, or commit and contain later `@`; `#` is for
+semantic fragments, not revisions.
 
 For a package or site docs topic, use `search` with `source:"docs"`.
 `docs_list` browses package pages, not standalone `site:` targets.

package/skills/githits-package/SKILL.md

@@ -21,7 +21,7 @@ Use GitHits package intelligence before making dependency claims from memory.
 
 - Most package commands use `<registry>:<name>[@<version>]`, for example `npm:lodash@4.17.20` or `pypi:requests`.
 - `pkg info` always reports the latest published version and does not accept a version pin.
-- `pkg changelog` accepts `<registry>:<name>` or `--repo-url <url>`; do not pass `<spec>@<version>` to changelog. Use `--to <version>` instead.
+- `pkg changelog` is package-only. Pin `@version` for one release; use `@from..to` or `--from`/`--to` for ranges. Repository and site targets are rejected.
 
 ## Core Commands
 
@@ -39,8 +39,8 @@ githits pkg deps npm:express --lifecycle all
 githits pkg deps npm:express --depth 3
 
 githits pkg changelog npm:express --limit 3
+githits pkg changelog npm:express@5.2.1
 githits pkg changelog npm:express --from 4.18.0 --to 4.19.0
-githits pkg changelog --repo-url https://github.com/expressjs/express --limit 2 --no-body
 
 githits pkg upgrade-review npm:zod@4.3.6 --to 4.4.3
 githits pkg upgrade-review --package npm:zod@4.3.6..4.4.3 --package npm:lint-staged@16.2.7..16.4.0
@@ -54,7 +54,7 @@ githits pkg upgrade-review --package npm:zod@4.3.6..4.4.3 --package npm:lint-sta
 - Need historical advisories that do not affect the inspected version: use `pkg vulns --scope non_affecting`; use `--scope all` for affected plus historical rows.
 - Need dependency footprint: start with `pkg deps`; add `--lifecycle all` for non-runtime groups and `--depth <n>` for aggregate transitive graph data.
 - Need upgrade evidence for dependency updates, outdated package bumps, or lockfile changes: prefer `pkg upgrade-review` because it compares current vs target vulnerabilities, changelog range evidence, deprecation metadata, peer changes, dependency changes, and transitive security evidence by default. It reports facts only; you still own the final assessment.
-- Need release notes without a current-to-target comparison: use `pkg changelog`; use `--from`/`--to` for ranges and `--no-body` for compact timelines.
+- Need release notes without a current-to-target comparison: use `pkg changelog`; `--no-body` for compact timelines.
 
 ## Gotchas
 

package/skills/githits-package/references/package.md

@@ -31,13 +31,11 @@ Use `--depth` to request capped transitive output. Without it, output is direct
 
 ## Changelog
 
-`githits pkg changelog <registry:name>` returns recent release notes. `--limit` caps latest mode. `--from` is the exclusive lower bound for range mode, which returns entries after `--from` through `--to` (or latest).
+`githits pkg changelog <registry:name[@version|@from..to]>` returns release notes for a package. Bare targets use latest mode. Pin `@version` for one selected release. Use `@from..to`, `@from..`, or `@..to` for interval and upper-cap forms.
 
-Flags: `--repo-url <url>`, `--from <version>`, `--to <version>`, `--limit 1-50`, `--git-ref <ref>`, `--verbose`, `--no-body`, `--json`.
+Flags: `--from <version>`, `--to <version>`, `--limit 1-50`, `--verbose`, `--no-body`, `--json`.
 
-Do not use `registry:name@version` for changelog. `--to <version>` is an upper cap, not an exact-release lookup.
-
-For repository changelogs, pass a full HTTPS URL on github.com, codeberg.org, or gitlab.com to `--repo-url`; use `--git-ref` for a branch or tag. Codeberg requires owner/repo; GitLab permits nested namespaces. Do not pass compact `github:`, `codeberg:`, or `gitlab:` targets to this URL field.
+`--from` and `--to` remain package range flags on a bare spec. Inline single-release targets reject those flags and `--limit`. Repository and site targets are not supported.
 
 ## Upgrade Review