letthemquibble 1.2.0 → 2.1.0

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 (3) hide show
  1. package/README.md +24 -6
  2. package/dist/quibble.js +1404 -728
  3. package/package.json +3 -7
package/README.md CHANGED
@@ -37,20 +37,32 @@ npm install -g letthemquibble
37
37
 
38
38
  Quibble talks to the hosted service at `https://api.letthemquibble.com` unless
39
39
  you name another endpoint. Create an account and an organization at
40
- <https://letthemquibble.com>, and have an admin create the project there.
41
- Then, in the repository:
40
+ <https://letthemquibble.com>. Then, in the repository:
42
41
 
43
42
  ```sh
44
43
  cd ~/code/myproject
45
- quibble login
46
- quibble init --org acme
44
+ quibble init
47
45
  quibble snippet --append CLAUDE.md --hook
48
46
  quibble complain "the build takes 4 minutes" -s high -t build
49
47
  quibble list
50
48
  quibble summary
51
49
  ```
52
50
 
53
- `quibble init` writes a `.quibblerc` and prints a short section for your
51
+ `quibble init` sets the repository up in one command. It names the project
52
+ after the git remote `origin`, or after the directory when there is no
53
+ remote. When you are not logged in yet, it logs you in through the browser.
54
+ It finds your organization in your account, and creates the project there
55
+ when it is missing and you are an admin. `--project`, `--org` and `--tag`
56
+ choose these yourself, and `--no-login` skips the login.
57
+
58
+ `quibble login` opens the browser, where you check the code and approve the
59
+ login. It needs no terminal, so a coding agent can start it too. Over SSH or
60
+ in WSL, open the printed URL on any device where you are signed in, or pass
61
+ `--no-browser` to print it alone. `quibble login --password` asks for the
62
+ email, the password and, when two-factor sign-in is on, a code in the
63
+ terminal instead.
64
+
65
+ `quibble init` also writes a `.quibblerc` and prints a short section for your
54
66
  `CLAUDE.md` or `AGENTS.md`. It tells the agent when to complain and how, for
55
67
  example:
56
68
 
@@ -68,6 +80,10 @@ file alone. `--hook` on `init`, `snippet` or `sync` adds a Claude Code
68
80
  `SessionStart` hook that runs `quibble sync --quiet` at the start of every
69
81
  new session, so the list stays current by itself.
70
82
 
83
+ Quibble refuses a complaint whose message or `--cmd` holds what looks like a
84
+ secret, such as an AWS access key, a GitHub token, an API key or a private
85
+ key. Remove the secret and file again. The snippet tells the agent so.
86
+
71
87
  Complaints that share a headline fold into one row of `quibble list`.
72
88
  `quibble show <id>` prints one in full, and any unique prefix of at least 6
73
89
  characters stands for an id. Project names ignore case: `DBT` and `dbt` are
@@ -98,6 +114,7 @@ once.
98
114
 
99
115
  For CI, a maintainer runs `quibble token create ci`, and the job sets the two
100
116
  lines it prints, `QUIBBLE_ENDPOINT` and `QUIBBLE_TOKEN`, instead of logging in.
117
+ A plain `quibble login` refuses to run when `CI` is set.
101
118
  A complaint that cannot reach the API waits in `~/.quibble/unsent.jsonl` and
102
119
  goes out with the next remote command, or with `quibble retry`.
103
120
 
@@ -105,5 +122,6 @@ Run `quibble --help` for every command.
105
122
 
106
123
  ## More
107
124
 
108
- - <https://github.com/repineap/quibble>
109
125
  - <https://letthemquibble.com>
126
+ - <https://letthemquibble.com/help>: install, update, setup and login
127
+ - Support: <support@letthemquibble.com>