slingit 0.2.1 → 0.2.2

package/README.md

@@ -67,7 +67,7 @@ Env takes precedence over the file; the file takes precedence over the built-in
 ## Loading a note (`pull`)
 
 ```bash
-npx slingit pull <url> [--comments]
+npx slingit pull <url> [--comments|--comments-only]
 ```
 
 Fetches a published note and prints its Markdown to stdout — handy for pulling an
@@ -84,9 +84,14 @@ note you shared. Comments on encrypted notes are decrypted locally with the same
 the comments cannot be fetched, the note body still prints and a one-line notice goes to
 stderr.
 
+With `--comments-only`, only the comments are fetched and printed — the note body is
+skipped entirely. Unlike `--comments`, a failure to fetch here is a hard error (there's
+nothing else to fall back to).
+
 | Flag | Description | Default |
 |---|---|---|
 | `--comments` | Also fetch reader comments and append them after the note body | off |
+| `--comments-only` | Fetch and print just the comments, skipping the note body | off |
 
 ## Skill installation
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "slingit",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "Share formatted Markdown notes via link. Encrypted by default (key in #URL), optional email delivery.",
   "type": "module",
   "bin": {

package/skill/SKILL.md

@@ -41,6 +41,14 @@ encrypted notes are decrypted locally with the same key from the `#` fragment. I
 has no comments yet, the section reads `## Comments (0)`; if the comments cannot be
 fetched, the note body still prints and a one-line notice goes to stderr.
 
+If you only care about the feedback and not the (already-known) note body — e.g. checking
+in on a note you slung earlier in the same session — use `--comments-only` instead to skip
+re-fetching and re-printing the whole document:
+
+```bash
+npx slingit pull <url> --comments-only
+```
+
 ## Choose the input method first
 
 Use the method that matches the user's request:

package/src/cli.js

@@ -8,7 +8,8 @@ const HELP = `slingit — share Markdown notes via link (encrypted by default)
 
 Usage:
   slingit shot [file.md] [flags]     publish a note (file or stdin)
-  slingit pull <url> [--comments]    fetch a note by link, print its Markdown to stdout
+  slingit pull <url> [--comments|--comments-only]
+                                     fetch a note by link, print its Markdown to stdout
   slingit install-skill [flags]      install the agent skill
   slingit help                       this help
 
@@ -40,6 +41,7 @@ pull decrypts locally too: it reads the note id from the URL path and the key fr
 the #fragment, fetches the ciphertext by id alone, and prints the Markdown. The key
 is never sent to the server. Pass the full link, including the part after #.
 Add --comments to also fetch reader feedback and append it as a Comments section.
+Use --comments-only to fetch just the comments, without the note body.
 `;
 
 export async function main(argv) {

package/src/pull.js

@@ -11,10 +11,23 @@ const ID_RE = /^[A-Za-z0-9_-]{10,14}$/;
  * reader, so the key never reaches the server — the iron rule stays intact.
  */
 export async function pull(args) {
-  const { url, comments: wantComments } = parseArgs(args);
+  const { url, comments: wantComments, commentsOnly } = parseArgs(args);
   const { id, origin, key } = parseUrl(url);
 
   const meta = await fetchMeta(origin, id);
+
+  if (commentsOnly) {
+    if (meta.mode !== 'public' && !key) {
+      throw new Error(
+        'this note is encrypted but the link has no key after "#" — you need the full link (including the #fragment) to read its comments'
+      );
+    }
+    const raw = await fetchComments(origin, id);
+    const normalized = await decryptComments(raw, meta, key);
+    process.stdout.write(formatCommentsSection(normalized, { standalone: true }));
+    return;
+  }
+
   const blob = await fetchBlob(origin, id);
 
   let markdown;
@@ -58,17 +71,22 @@ export async function pull(args) {
 function parseArgs(args) {
   let url = null;
   let comments = false;
+  let commentsOnly = false;
   for (const a of args) {
     if (a === '--comments') {
       comments = true;
       continue;
     }
+    if (a === '--comments-only') {
+      commentsOnly = true;
+      continue;
+    }
     if (a.startsWith('-')) throw new Error(`unknown flag "${a}". See: slingit help`);
     if (url) throw new Error('only one URL can be given');
     url = a;
   }
-  if (!url) throw new Error('usage: slingit pull <url> [--comments]');
-  return { url, comments };
+  if (!url) throw new Error('usage: slingit pull <url> [--comments|--comments-only]');
+  return { url, comments, commentsOnly };
 }
 
 function parseUrl(input) {
@@ -160,11 +178,16 @@ async function decryptComments(raw, meta, key) {
 }
 
 /**
- * Render a normalized comments array as a Markdown section appended after the
- * note body. Pure and self-contained so it can be unit-tested without a server.
+ * Render a normalized comments array as a Markdown section. By default it's
+ * appended after the note body (so it opens with a `---` separator); pass
+ * `standalone: true` for `--comments-only` output, which has no document above
+ * it to separate from. Pure and self-contained so it can be unit-tested without
+ * a server.
  */
-export function formatCommentsSection(comments) {
-  let out = `\n---\n\n## Comments (${comments.length})\n\n`;
+export function formatCommentsSection(comments, { standalone = false } = {}) {
+  let out = standalone
+    ? `## Comments (${comments.length})\n\n`
+    : `\n---\n\n## Comments (${comments.length})\n\n`;
   if (comments.length === 0) {
     return `${out}_No comments yet._\n`;
   }