boost-skill-cli 1.0.30__tar.gz → 1.0.31__tar.gz

{boost_skill_cli-1.0.30 → boost_skill_cli-1.0.31}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.0.30
+Version: 1.0.31
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License: GNU GENERAL PUBLIC LICENSE

{boost_skill_cli-1.0.30 → boost_skill_cli-1.0.31}/boost_cli/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '1.0.30'
-__version_tuple__ = version_tuple = (1, 0, 30)
+__version__ = version = '1.0.31'
+__version_tuple__ = version_tuple = (1, 0, 31)
 
 __commit_id__ = commit_id = None

{boost_skill_cli-1.0.30 → boost_skill_cli-1.0.31}/boost_cli/commands/pkg.py

@@ -176,7 +176,10 @@ def cmd_uninstall(argv: List[str]) -> int:
         out.ok("removed %s" % _tilde(dest))
         removed += 1
     if removed:
-        out.info("Uninstalled %s" % _plural(removed, "skill"))
+        lines = ["Uninstalled %s" % _plural(removed, "skill")]
+        if removed == 1 and len(args.names) == 1:
+            lines.append(out.c("next: boost list", out.DIM))
+        print(out.panel(lines, title="removed", hue="pink"))
     return 1 if failed else 0
 
 

{boost_skill_cli-1.0.30 → boost_skill_cli-1.0.31}/boost_skill_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.0.30
+Version: 1.0.31
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License: GNU GENERAL PUBLIC LICENSE

{boost_skill_cli-1.0.30 → boost_skill_cli-1.0.31}/docs/design-roadmap.html

@@ -438,9 +438,9 @@
         <article class="ritem" data-track="commands" data-impact="med">
           <div class="ritem-top"><span class="rid">BOOST-D25</span><span class="rstatus proposed">Proposed</span></div>
           <h4>Branded usage &amp; error output</h4>
-          <p>Run a subcommand wrong — <code>boost snapshot</code> with no action — and you get raw, unstyled <code>argparse</code>: a multi-line usage dump with a bare <code>error:</code>, nothing like the branded help. Route argparse's usage/error through the Aurora output layer (accent the program name, dim the usage grammar, use the standard <code>Error:</code> affordance) so <em>failure</em> looks as designed as success. Bonus: a "did you mean …" suggestion for unknown commands.</p>
-          <div class="rmeta"><span class="m-cat">ux</span><span>Complexity M</span><span class="m-imp med">Impact Med</span><span class="m-wow">★★★☆☆</span></div>
-          <div class="rref"><code>cli.py · argparse formatter</code></div>
+          <p>Grading confirmed this hits <b>every command with a required argument</b> — <code>boost uninstall</code>, <code>boost snapshot</code> and more all dump raw, unstyled <code>argparse</code>: a multi-line usage block with a bare <code>error:</code>, nothing like the branded top-level dispatch (which already routes through <code>Error:</code> + a difflib "did you mean"). The durable fix is a shared <code>BoostArgumentParser</code> subclass whose <code>error()</code>/usage route through the Aurora output layer, adopted across the ~50 per-command parsers — a broad, test-first sweep, so logged rather than rushed.</p>
+          <div class="rmeta"><span class="m-cat">ux</span><span>Complexity L</span><span class="m-imp med">Impact Med</span><span class="m-wow">★★★☆☆</span></div>
+          <div class="rref"><code>core · new BoostArgumentParser · commands/*.py</code></div>
         </article>
 
       </div>

{boost_skill_cli-1.0.30 → boost_skill_cli-1.0.31}/docs/roadmap.html

@@ -116,7 +116,7 @@
       <div class="stat"><b>4</b><span>Shipped</span></div>
       <div class="stat"><b>3</b><span>Next up</span></div>
       <div class="stat"><b>4</b><span>Planned</span></div>
-      <div class="stat"><b>16</b><span>Loop finds</span></div>
+      <div class="stat"><b>24</b><span>Loop finds</span></div>
     </div>
   </section>
 
@@ -596,6 +596,142 @@
     </div>
   </section>
 
+  <!-- ============ DEVELOPER EXPERIENCE & MAINTAINABILITY ============ -->
+  <section class="block reveal" id="dx">
+    <div class="block-head">
+      <h2>Developer experience &amp; maintainability</h2>
+      <span class="count">// planned · free tooling to catch issues earlier &amp; keep the code legible</span>
+      <span class="rule"></span>
+    </div>
+    <div class="rgrid">
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">DX · Infra</span></div>
+        <h3>Shift-left gate — <code>pre-commit</code> + pre-commit.ci</h3>
+        <p>A <code>.pre-commit-config.yaml</code> runs ruff, mypy, codespell and the
+           whitespace fixers <em>before</em> code ever reaches CI, and the free-for-OSS
+           <strong>pre-commit.ci</strong> auto-fixes and auto-updates hooks right on the
+           PR. The foundation the rest of this section plugs into — one config,
+           many checks, faster feedback.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m hi">Impact <b>High</b></span>
+          <span class="m">Wow <b class="wow">★★★★</b></span>
+          <span class="m">auto-fix PRs</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Quality · Architecture</span></div>
+        <h3>Layering guard — <code>import-linter</code></h3>
+        <p>Enforce the architecture boost already assumes: <code>core/</code> must
+           never import <code>commands/</code>, and the CLI depends inward only.
+           <code>import-linter</code> turns that contract into a CI check, catching
+           the cross-layer imports that slowly erode a clean engine — a structural
+           smell no line-level linter can see.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>M</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★★★</b></span>
+          <span class="m">core/ ↛ commands/</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Quality · Docs</span></div>
+        <h3>Typo detection — <code>codespell</code></h3>
+        <p>Cheap, high-signal for a project this documentation-heavy: scan the
+           README, <code>docs/*.html</code>, docstrings and every user-facing CLI
+           string for misspellings. A typo in <code>boost --help</code> is a bug
+           users see on their first run.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★</b></span>
+          <span class="m">user-facing text</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Quality · Docs</span></div>
+        <h3>Docstring coverage — <code>interrogate</code></h3>
+        <p>Gate CI below a docstring-coverage threshold so the engine stays
+           self-documenting as it grows. <code>core/</code> is already well
+           commented; <code>interrogate</code> keeps it that way and flags the
+           new public function that shipped without a word of explanation.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m">Impact <b>Low</b></span>
+          <span class="m">Wow <b class="wow">★★</b></span>
+          <span class="m">keeps core/ documented</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Testing · Perf</span></div>
+        <h3>Performance-regression gate — <code>pytest-benchmark</code></h3>
+        <p>Benchmark the hot paths — a catalog scan over a large skills tree, a
+           registry load — and fail the build when a change regresses them past a
+           threshold. Catches the <em>performance</em> bugs a correctness suite
+           waves through: the O(n²) that only bites at scale.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>M</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★★</b></span>
+          <span class="m">scan &amp; registry</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Quality · Smell</span></div>
+        <h3>Modernization smells — <code>refurb</code> + <code>pyupgrade</code></h3>
+        <p><code>refurb</code>'s unique <code>FURB</code> checks flag dated idioms
+           the ruff families miss, and <code>pyupgrade</code> rewrites to the
+           cleanest form the <code>&gt;=3.9</code> floor allows. Keeps the codebase
+           reading like modern Python instead of accreting legacy patterns.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m">Impact <b>Low</b></span>
+          <span class="m">Wow <b class="wow">★★</b></span>
+          <span class="m">respects 3.9 floor</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Testing · Platform</span></div>
+        <h3>Coverage dashboard — Codecov (free for OSS)</h3>
+        <p>Upgrade the homegrown coverage badge to Codecov's PR diff-coverage
+           comments, file sunburst and trend graph — free for public repos. The
+           hosted counterpart to the self-contained <code>diff-cover</code> gate:
+           one enforces patch coverage in CI, the other visualizes the trend over
+           time.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★★</b></span>
+          <span class="m">PR decoration</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Security · CI/CD</span></div>
+        <h3>Runner egress monitoring — StepSecurity Harden-Runner</h3>
+        <p>Free for public repos, Harden-Runner watches (and can block) unexpected
+           network egress from CI runners — the runtime signal that catches a
+           compromised action exfiltrating a token. The dynamic complement to
+           <code>zizmor</code>'s static workflow analysis, guarding the release
+           path from both sides.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★★★</b></span>
+          <span class="m">runtime + static</span>
+        </div>
+      </article>
+
+    </div>
+  </section>
+
   <footer>
     <p>Maintained by the boost quality loop · themed with
        <a href="../style/boost.css">style/boost.css</a> ·

{boost_skill_cli-1.0.30 → boost_skill_cli-1.0.31}/tests/functional/test_cli_pkg.py

@@ -102,6 +102,7 @@ class TestUninstall:
         assert "nope: nope is not installed" in r.out
         assert "unlinked ← claude-code · windsurf · cursor" in r.out
         assert "Uninstalled 2 skills" in r.out
+        assert "╭─ removed" in r.out               # D13: framed summary card
         assert _lock() == {}
         assert not (paths.store_dir() / "brainstorming").exists()
         assert not (paths.store_dir() / "commit-messages").exists()