feat: make loop-engineering super useful (interactive tools, loop-audit v1.4, new Issue Triage pattern)#12
Closed
cobusgreyling wants to merge 1 commit into
Closed
Conversation
- loop-audit v1.4: dynamic 'loopActivity' signal (git history, 'Last run' timestamps in STATE, scheduled workflows, run logs). L3 now requires real usage evidence (not just files). Stronger --suggest output and recommendations. Updated tests + README. - GitHub Pages showcase: Interactive Pattern Picker (click symptom pills → exact npx + first /loop command + links). Live Readiness Simulator (checkboxes for all signals → live score + level + next action, mirrors computeScore + new L3 rules). Hero now has prominent one-click copy npx CTAs for loop-init and loop-audit. - New low-risk pattern: Issue Triage (perfect companion to Daily Triage for noisy GitHub/Linear issues). 7 patterns total. Updated registry.yaml (validated), patterns/README, pattern-picker.md decision flow + table. - Polish: loop-init bumped to 1.2.0. Main + tool READMEs, badges, and quickstart language updated to emphasize 'npx works today' and the new interactive tools + activity proof requirement. Builds and validation green. All changes dogfood the philosophy: structure + actual runs = high L3 score.
Contributor
Loop Readiness AuditScore: 100/100 (L3) Strong loop readiness — good candidate for L3 with explicit gates. No suggestions — looking good. Posted by |
Owner
Author
|
Superseded by #16 (rebased on main with loop-cost + combined L3 rules). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR implements major improvements to make the
loop-engineeringrepo significantly more useful and adoptable.Highlights
loop-audit v1.4.0
loopActivitysignal that detects real usage: git history of STATE updates, "Last run" timestamps in state files, scheduled workflows, and run logs.Interactive GitHub Pages Showcase
npxcommands in the hero.npx @cobusgreyling/loop-init ...command + recommended first/loopprompt + links.New low-risk pattern: Issue Triage
loop-initsupport.Distribution & Polish
loop-auditbumped to 1.4.0,loop-initto 1.2.0.npxworks immediately with no clone required.Verification
loop-audit+loop-init)scripts/before-after-demo.shworksloop-audit . --suggeston the repo shows 100 + activity signalsThe feature branch was used for development. This PR follows the repository's branch protection rules.
How to review / test
npx @cobusgreyling/loop-audit . --suggest(after the packages are published, or run from source).Once checks pass (the existing audit + validate workflows will run), this can be merged.