You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a2da9d0
Browse filesBrowse the repository at this point in the historyBrowse files
- 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.
Co-authored-by: Cobus Greyling <cobusgreyling@Cobuss-MacBook-Pro-2.local>
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,8 +52,9 @@ Also add an entry to `patterns/registry.yaml`.
52
52
53
53
## Community
54
54
55
-
-**Questions**: open an issue with label `question` or `pattern-request`
56
-
-**Discussions**: enable GitHub Discussions on the repo for pattern Q&A (recommended for maintainers)
55
+
-**Questions**: [GitHub Discussions](https://github.com/cobusgreyling/loop-engineering/discussions) (preferred) or issue with label `question`
56
+
-**Show your loop**: post in Discussions or add a row to [docs/adopters.md](./docs/adopters.md)
57
+
-**Good first issues**: look for label [`good first issue`](https://github.com/cobusgreyling/loop-engineering/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
57
58
-**Security**: see [SECURITY.md](./SECURITY.md) — do not file public issues for exploitable vulnerabilities
58
59
59
60
Thank you for helping make this the go-to reference for loop engineering.
Not sure which to pick? See[pattern-picker](docs/pattern-picker.md).
114
+
Not sure which to pick? Try the [interactive picker](https://cobusgreyling.github.io/loop-engineering/#interactive) or[pattern-picker](docs/pattern-picker.md).
/loop 1d Run loop-triage. Update STATE.md. No auto-fix in week one.
132
135
```
133
136
134
-
Packages publish from tagged releases — see [docs/RELEASE.md](docs/RELEASE.md). Until npm is live, run from this repo:
137
+
All three CLIs publish to npm from tagged releases — see [docs/RELEASE.md](docs/RELEASE.md). No clone required.
138
+
139
+
**Develop from source** (monorepo contributors):
135
140
136
141
```bash
137
142
cd tools/loop-init && npm ci && npm test&& node dist/cli.js /path/to/project --pattern daily-triage --tool grok
@@ -173,7 +178,7 @@ Addy Osmani:
173
178
174
179
## Contributing
175
180
176
-
Share production patterns, tool mappings, and failure stories. See [CONTRIBUTING.md](CONTRIBUTING.md) and [GitHub Discussions](https://github.com/cobusgreyling/loop-engineering/discussions).
181
+
Share production patterns, tool mappings, and failure stories. See [CONTRIBUTING.md](CONTRIBUTING.md), [adopters](docs/adopters.md), and [GitHub Discussions](https://github.com/cobusgreyling/loop-engineering/discussions).
*Your project here — see [CONTRIBUTING.md](../CONTRIBUTING.md).*
24
+
25
+
## Show & tell
26
+
27
+
Prefer chat over a PR? Post in [GitHub Discussions → Show your loop](https://github.com/cobusgreyling/loop-engineering/discussions/categories/show-your-loop) with:
28
+
29
+
1. Which pattern you picked and why
30
+
2. Your first `/loop` or scheduler command
31
+
3. One surprise (good or bad)
32
+
33
+
Failure reports are first-class — see [stories/](../stories/).
0 commit comments