housebroken-cli 0.2.1__tar.gz → 0.2.2__tar.gz

{housebroken_cli-0.2.1 → housebroken_cli-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: housebroken-cli
-Version: 0.2.1
+Version: 0.2.2
 Summary: Agent-written pull requests that do not make a mess in someone else's house.
 Project-URL: Repository, https://github.com/lenamonj/housebroken
 License-Expression: MIT

{housebroken_cli-0.2.1 → housebroken_cli-0.2.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "housebroken-cli"
-version = "0.2.1"
+version = "0.2.2"
 description = "Agent-written pull requests that do not make a mess in someone else's house."
 dynamic = ["readme"]
 license = "MIT"

{housebroken_cli-0.2.1 → housebroken_cli-0.2.2}/skills/housebroken/SKILL.md

@@ -68,7 +68,11 @@ report it in one line and do not proceed to the next step.
    On a fresh clone of the upstream default branch, not the tree you found
    the bug in, write the test that fails. Run it and keep the failing output.
    Apply the patch. Run it again. Both results go into the pull request as
-   the test itself; the body states the fact in one sentence.
+   the test itself; the body states the fact in one sentence. When the
+   patched function serves several public entry points or has several
+   branches, the test is a grid: every entry point through every branch,
+   plus the zero, identity and signed-boundary rows. A reviewer lists the
+   empty cells otherwise.
 
 5. **Run their CI, not yours.**
    Run the project's own test target on the fresh clone, and every gate its
@@ -116,13 +120,31 @@ report it in one line and do not proceed to the next step.
     `housebroken verify owner/repo PR` re-derives from GitHub that the head is
     the intended commit, the diff is exactly the intended files, and CI
     settled. `housebroken sweep` lists every open pull request where the ball
-    is in your court. Answer every maintainer comment the same day, in the
-    user's voice, after reading the whole thread. Rework what is asked for as
-    a second commit so the reviewer sees the change. When the maintainer is
+    is in your court. Before saying anything about a thread, read every
+    comment body, review and timeline event newer than your last own action;
+    a list of who commented is not a read, and a conversion to draft is a
+    review. Answer every maintainer comment the same day, in the user's
+    voice. Rework what is asked for as a second commit so the reviewer sees
+    the change. When the maintainer is
     right, concede in one sentence and let them close it. Never nudge a
     silent maintainer without the user's explicit word. After answering a
     review, record what the maintainer asked for with
     `housebroken notes owner/repo add "..."`.
+    Write the reply the way one maintainer writes to another. Lead with the
+    fact or the action, never with a verdict on the reviewer: no "you are
+    right", "good catch", "great point", "thanks for the feedback", no
+    apology, no restating their question, no closing summary or offer of
+    further help. A concession is the corrected fact followed by what
+    changed: "Every loader checks its read, so a truncated file fails on
+    main; the description is corrected." A disagreement is the command and
+    its result, without adjectives. An answer to a question is the answer
+    first and the evidence second. One to three sentences, no bullet list
+    under a paragraph's worth of content, no bold, no exclamation mark, no
+    handle unless the thread has several people. Offer closure as a plain
+    statement ("Fine to close."), and stop when the content stops.
+    Never post two replies to one repository in the same minute: space them
+    at least ten minutes apart, the one that matters most first, so a
+    maintainer's inbox does not show three answers stamped the same second.
 
 11. **Clean up.**
     `housebroken hygiene` deletes the fork branch of every merged or closed
@@ -135,6 +157,8 @@ report it in one line and do not proceed to the next step.
     finding, each passing every step above on its own. GitHub lets
     maintainers cap open pull requests from non-collaborators and counts
     agent-opened ones against that cap.
+    The same spacing applies to filing: pull requests and issues on one
+    repository go out at least ten minutes apart, the strongest first.
 
 13. **Write it down before you leave.**
     A run through the door ends with its ledger, not with the pull