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
Copy file name to clipboardExpand all lines: .agents/tasks/2025/05/30-1219-refactor-gems
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,9 @@
1
1
A previous developer got the following task:
2
2
3
-
Currently, the gems in the repo are structured in a weird way. We have a very think executable file for each gem that just calls into another ruby script that used to be the primary executable. The other script now serves as a library, but has special code to detect when it's being executed. Let's make the second script a pure library and move all the "executable" code in the main gem binaries.
3
+
> Make sure the functionality of both gems is usable as a library. The gem binaries
4
+
> should just call into methods exported by the gem libraries. Make command-line
5
+
> handling consistent between the two gems. Use class names that are derived from
6
+
> the gem names.
4
7
5
8
He made really good progress in commit d007872908d4fb5dbe862549f825eec98e7721f0, but
0 commit comments