add scope to performance scout

Author: dagda1

.changeset/large-deer-camp.md

@@ -0,0 +1,5 @@
+---
+"@cutting/performance-scout": minor
+---
+
+add performance-scout to npm

packages/performance-scout/package.json

@@ -1,6 +1,10 @@
 {
   "name": "@cutting/performance-scout",
+<<<<<<< HEAD
   "version": "0.1.0",
+=======
+  "version": "0.0.0",
+>>>>>>> 3448a362 (add scope to performance scout)
   "type": "module",
   "publishConfig": {
     "access": "public"

plans/better-prs.md

@@ -11,7 +11,11 @@
 - AI favours volume over precision and ownership
 - You wouldn't accept a 100-file PR from a new dev - don't accept it from AI
 - Don't reverse decades of hard-won practices (DRY, small PRs, code ownership) just because AI makes it easy to generate code, these came about because things when wrong
+<<<<<<< HEAD
 - PR reviews now take forever - too much volume for the eye to take in
+=======
+- PR reviews could take forever or just ignored - too much volume for the eye to take in
+>>>>>>> 3448a362 (add scope to performance scout)
 - Open source/existing code has tests, is battle-hardened from real use, and edge cases are already solved - AI code has none of that
 
 ## Practical Steps
@@ -23,10 +27,21 @@
 - Sonar/jscpd can detect duplicated functions within the same PR
 - Fail/warn on large new files (Danger.js or CI script to flag any new file over X lines)
 - Fail/warn if a PR grows an existing file by more than Y lines
+<<<<<<< HEAD
 - Manually viewing the PR is the last step but still important
+=======
+- Manually reviewing the PR is the last step but still important
+>>>>>>> 3448a362 (add scope to performance scout)
 
 ## AI Doesn't Extend, It Recreates
 
 - When adding to complex existing code, AI errs on the side of caution and recreates everything instead of extending
 - Example: DSL-to-react-json-schema-form transformer - adding a new feature resulted in an 800+ line file that recreated all types (weaker), all functions (worse), instead of extending what was there
 - Funny side effect: GitHub hides large files by default - I missed the 800 page monster in the PR review initially :)
+<<<<<<< HEAD
+=======
+
+## citations
+
+- [SonarSource blog on poor code quality growth in AI-accelerated codebases](https://www.sonarsource.com/blog/the-inevitable-rise-of-poor-code-quality-in-ai-accelerated-codebases)
+>>>>>>> 3448a362 (add scope to performance scout)