PyPI - codingest - Versions diffs - 0.2.18__tar.gz → 0.2.19__tar.gz - Mend

codingest 0.2.18tar.gz → 0.2.19tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (105) hide show

{codingest-0.2.18 → codingest-0.2.19}/Cargo.lock RENAMED Viewed

@@ -302,7 +302,7 @@ dependencies = [
 [[package]]
 name = "codingest"
-version = "0.2.18"
+version = "0.2.19"
 dependencies = [
  "aho-corasick",
  "base64 0.22.1",
@@ -338,7 +338,7 @@ dependencies = [
 [[package]]
 name = "codingest-cli"
-version = "0.2.18"
+version = "0.2.19"
 dependencies = [
  "anyhow",
  "clap",
@@ -350,7 +350,7 @@ dependencies = [
 [[package]]
 name = "codingest-mcp"
-version = "0.2.18"
+version = "0.2.19"
 dependencies = [
  "anyhow",
  "codingest",
@@ -359,7 +359,7 @@ dependencies = [
 [[package]]
 name = "codingest-py"
-version = "0.2.18"
+version = "0.2.19"
 dependencies = [
  "codingest",
  "codingest-cli",

{codingest-0.2.18 → codingest-0.2.19}/Cargo.toml RENAMED Viewed

@@ -3,7 +3,7 @@ members = ["crates/codingest", "crates/codingest-cli", "crates/codingest-mcp", "
 resolver = "2"
 [workspace.package]
-version = "0.2.18"
+version = "0.2.19"
 edition = "2021"
 rust-version = "1.88"
 license = "MIT"

{codingest-0.2.18 → codingest-0.2.19}/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codingest
-Version: 0.2.18
+Version: 0.2.19
 Classifier: Development Status :: 3 - Alpha
 Classifier: Intended Audience :: Developers
 Classifier: Programming Language :: Python :: 3

{codingest-0.2.18 → codingest-0.2.19}/crates/codingest-cli/Cargo.toml RENAMED Viewed

@@ -14,7 +14,7 @@ name = "codingest"
 path = "src/main.rs"
 [dependencies]
-codingest = { version = "0.2.18", path = "../codingest" }
+codingest = { version = "0.2.19", path = "../codingest" }
 kglite = { workspace = true }
 anyhow = "1.0.104"
 clap = { version = "4.6.4", features = ["derive"] }

{codingest-0.2.18 → codingest-0.2.19}/crates/codingest-cli/skills/codingest-code-review/SKILL.md RENAMED Viewed

@@ -14,43 +14,60 @@ git diff, source reading, and literal-text search; it does not replace them.
 > `pip install codingest` provides both plus the builder-aware
 > `codingest-mcp` server. Rust-only environments can alternatively use Cargo.
-1. Inspect the diff and repository guidance first. Identify changed symbols and
-   the base/head revisions.
-2. Build or refresh the graph without executing repository code:
-   ```bash
-   codingest build . --output .kglite/code-review.kgl --format json
-   ```
-   For a committed comparison, use one graph spanning both revisions:
-   ```bash
-   codingest build . --revs '<base>' '<head>' \
-     --output .kglite/code-review.kgl --format json
-   ```
-3. Always discover the actual schema before writing Cypher:
-   ```bash
-   kglite describe .kglite/code-review.kgl --connections --cypher
-   ```
-4. Query the smallest structural question that can confirm or reject a review
-   hypothesis. Use JSON for agent parsing:
-   ```bash
-   kglite query .kglite/code-review.kgl '<cypher>' --format json
-   ```
-5. Open every implicated file and verify the behavior at exact lines. Report
-   only findings supported by source evidence. Do not infer runtime behavior
-   from an edge alone.
-6. Before reusing an artifact, check freshness:
-   ```bash
-   codingest status --output .kglite/code-review.kgl --format json
-   ```
+Inspect the diff and repository guidance first. Identify changed symbols and
+the base/head revisions, then build or refresh the graph without executing
+repository code:
+```bash
+codingest build . --output .kglite/code-review.kgl --format json
+```
+For a committed comparison, use one graph spanning both revisions:
+```bash
+codingest build . --revs '<base>' '<head>' \
+  --output .kglite/code-review.kgl --format json
+```
+Before reusing an artifact, check freshness:
+```bash
+codingest status --output .kglite/code-review.kgl --format json
+```
+## Retrieve only what answers the question
+Choose the narrowest route for the uncertainty in front of you; these are
+alternatives, not a compulsory sequence. Reuse tool signatures already known
+in the current session; if a needed tool is not visible, discover that tool
+rather than loading a broad catalog.
+- **Known symbol or location:** read it directly. With MCP, use
+  `read_code_source` for a qualified name or `read_source` for a path, applying
+  `start_line`, `end_line`, and `max_chars` when a full body or file is not
+  needed.
+- **Exact structural question:** use `cypher_query`, or `kglite query` at the
+  CLI. Reuse a schema already observed for the same unchanged graph. Otherwise
+  inspect only the needed node or connection shape with `graph_overview` or
+  `kglite describe`; do not retrieve the whole schema by habit.
+- **Broad explanation or unfamiliar subsystem:** use bounded `explore`, starting
+  with a short topic, a few `max_entities`, shallow `max_depth`, and
+  `include_source: false` unless bodies are needed. Narrow to selected symbols
+  before reading source.
+- **Literal text:** use grep/ripgrep for error strings, comments, and config
+  keys, then open only the relevant matches.
+Every additional read should resolve a concrete uncertainty needed for the
+answer. Project only useful Cypher properties, return a few relevant candidates,
+and exclude unrelated fixtures, generated code, vendors, or examples when the
+question does not cover them. If output truncates, narrow the query or source
+range instead of repeatedly increasing output. Reuse evidence already seen
+unless its source or active graph changed.
+Open implicated code at exact lines before claiming behavior; an edge alone is
+not runtime proof. Stop when the requested conclusions are supported. Expand
+only for a contradiction, missing evidence, or a correctness risk that could
+change the answer.
 See [queries.md](references/queries.md) for query patterns,
 [public-repositories.md](references/public-repositories.md) for safe public-repo
@@ -88,7 +105,8 @@ prior question — what is eligible to be a finding at all.
 ## Honesty rules
-- Never invent labels, properties, or connection types: `describe()` first.
+- Never invent labels, properties, or connection types. Discover an unfamiliar
+  shape before querying it; reuse a known shape while the graph is unchanged.
 - Treat unresolved or missing graph edges as absence of evidence, not proof.
 - Quote paths and revisions passed through the shell.
 - Never build, import, or execute code from a repository merely to review it.

{codingest-0.2.18 → codingest-0.2.19}/crates/codingest-cli/skills/codingest-code-review/references/public-repositories.md RENAMED Viewed

@@ -18,3 +18,13 @@ For an existing cache, fetch only the explicit refs needed. The revision build
 uses `git archive` and never checks out or runs the repository. Do not silently
 switch a user's working checkout. Verify GitHub claims against the resolved
 commit and cite stable source links when reporting findings.
+## Keep repository investigations bounded
+When using the open-source MCP, activate the requested repository and revision,
+then follow the routing policy in the parent skill. Reuse tool signatures and
+schema shapes already observed for the same active graph. If a tool or shape is
+unknown, discover only that tool or the node/connection types needed for the
+next query; broad tool catalogs and full schemas are not prerequisites. Start
+from the named symbol or subsystem, and exclude fixtures, generated sources,
+vendored trees, and examples unless they bear on the question.

{codingest-0.2.18 → codingest-0.2.19}/crates/codingest-cli/skills/codingest-code-review/references/queries.md RENAMED Viewed

@@ -1,7 +1,9 @@
 # Code-review query patterns
-Run `kglite describe <graph> --connections --cypher` first and adapt these
-patterns to the labels and properties it reports.
+Adapt these patterns to the labels and properties already known for the active
+graph. If the needed node or connection shape is unfamiliar, inspect that shape
+with `graph_overview` or `kglite describe <graph> --connections --cypher` before
+querying it.
 Find a symbol before asking about its relationships:

{codingest-0.2.18 → codingest-0.2.19}/crates/codingest-mcp/Cargo.toml RENAMED Viewed

@@ -14,6 +14,6 @@ name = "codingest-mcp"
 path = "src/main.rs"
 [dependencies]
-codingest = { version = "0.2.18", path = "../codingest" }
+codingest = { version = "0.2.19", path = "../codingest" }
 kglite-mcp-server = { workspace = true }
 anyhow = "1.0.104"

{codingest-0.2.18 → codingest-0.2.19}/crates/codingest-py/Cargo.toml RENAMED Viewed

@@ -42,7 +42,7 @@ doctest = false
 pyo3 = { version = "0.29" }
 # The engine-free builder (parsers, call/type/route edges, rev merge, repo
 # clone, manifest reader). Docs pass gated by this crate's `docs` feature.
-codingest = { version = "0.2.18", path = "../codingest", default-features = false }
+codingest = { version = "0.2.19", path = "../codingest", default-features = false }
 # `.kgl` persistence (`kglite::api::io::save_graph`) for the serialize half of
 # the build-then-load handoff, plus the `DirGraph` type the builder returns.
 kglite = { workspace = true }
@@ -53,9 +53,9 @@ tempfile = "3.27.0"
 # through `_run_cli`, so `pip install codingest` also installs the `codingest`
 # command without a second wheel or a duplicated builder build. Mirrors
 # kglite-py's `kglite-cli` bundling.
-codingest-cli = { version = "0.2.18", path = "../codingest-cli" }
+codingest-cli = { version = "0.2.19", path = "../codingest-cli" }
 # Source-building MCP composition. The graph server and generic MCP lifecycle
 # remain owned by its existing kglite-mcp-server -> mcp-methods Rust dependency
 # chain; linking this thin library into the extension gives pip users the same
 # builder-aware server as the standalone `codingest-mcp` binary.
-codingest-mcp = { version = "0.2.18", path = "../codingest-mcp" }
+codingest-mcp = { version = "0.2.19", path = "../codingest-mcp" }