codecall 1.2.1 → 1.2.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md
CHANGED
|
@@ -1,5 +1,7 @@
|
|
|
1
1
|
# codecall
|
|
2
2
|
|
|
3
|
+
[**Website**](https://codecall-theta.vercel.app/) · [npm](https://www.npmjs.com/package/codecall) · [GitHub](https://github.com/GAURAV-1313/codecall)
|
|
4
|
+
|
|
3
5
|
**codecall teaches you the code you just wrote.**
|
|
4
6
|
|
|
5
7
|
After you (or your AI coding assistant) finish building something, codecall
|
|
@@ -72,6 +74,14 @@ is the wrong call (like after a non-idempotent request that already went
|
|
|
72
74
|
through). Same short format — a couple of ideas, a couple of questions, a
|
|
73
75
|
summary — just grounded in whatever you actually built.
|
|
74
76
|
|
|
77
|
+
Or say your assistant added a database index to speed up a slow query.
|
|
78
|
+
codecall would recommend a session on *why* that specific index helps — how
|
|
79
|
+
the query planner uses it, which column order matters, and when an index
|
|
80
|
+
actually hurts (like on a write-heavy table). It would teach that using your
|
|
81
|
+
real schema and query, then check whether you can predict which future queries
|
|
82
|
+
this index will and won't help. Same short format — a couple of ideas, a
|
|
83
|
+
couple of questions, a summary — grounded in the change you just made.
|
|
84
|
+
|
|
75
85
|
## Requirements
|
|
76
86
|
|
|
77
87
|
- Codex or Claude Code, already installed.
|
package/package.json
CHANGED