WIP: A simple cli for daily tangled use cases and AI integration. This is for my personal use right now, but happy if others get mileage from it! :)
Update project status in TODO.md
+16
-13
+16
-13
TODO.md
+16
-13
TODO.md
···
27
27
28
28
## Context Engine (Git Integration)
29
29
30
-
- [ ] Develop a "Context Resolver" module to infer repository context (DID) from the current working directory.
31
-
- [ ] Start by using the current Git repository context.
32
-
- [ ] Integrate `git-url-parse` to resolve Tangled DID/NSID from `.git/config` remote URLs. Using `simple-git` if needed.
33
-
- [ ] If multiple remotes exist, look for one at tangled.org, then prompt the user to select remote if ambiguity remains.
34
-
- [ ] Fallback to prompting the user to add a remote for their Tangled repository if none are found.
35
-
- [ ] Avoid creating a config file in V1; rely on Git remotes and CLI flags for context.
36
-
- [ ] If a config is needed remember that the precedence order should be: CLI flags > local config > home folder config. Users may prefer different settings per repo (such as unique remote names, etc).
30
+
- [x] Develop a "Context Resolver" module to infer repository context (DID) from the current working directory.
31
+
- [x] Start by using the current Git repository context.
32
+
- [x] Integrate `git-url-parse` to resolve Tangled DID/NSID from `.git/config` remote URLs. Using `simple-git` if needed.
33
+
- [x] If multiple remotes exist, look for one at tangled.org, then prompt the user to select remote if ambiguity remains.
34
+
- [x] Fallback to prompting the user to add a remote for their Tangled repository if none are found.
35
+
- [x] Avoid creating a config file in V1; rely on Git remotes and CLI flags for context.
36
+
- [x] If a config is needed remember that the precedence order should be: CLI flags > local config > home folder config. Users may prefer different settings per repo (such as unique remote names, etc).
37
37
38
38
## Issue Management
39
39
···
41
41
- [ ] Implement `tangled issue list [--json "id,title"]` command.
42
42
- [ ] Support `--json` output with field filtering.
43
43
- [ ] Migrate this TODO list into Tangled issues once issue creation is implemented. (note defects and address blocking features as needed).
44
-
45
-
## Repository Management
46
-
47
-
- [ ] Implement `tangled repo create <repo-name>` command.
48
-
- [ ] Implement `tangled repo view` command (display repo details).
49
-
- [ ] Support `--json` output with field filtering (e.g., `--json name,cloneUrl,description`) using `lodash/pick`).
44
+
- [ ] Create phases in this todo list, and then use `- [ ]` tasks in the issue descriptions.
45
+
- [ ] Remove TODO.md once all tasks are migrated to issues.
50
46
51
47
## Pull Request Management
52
48
···
63
59
- [ ] Implement `tangled pr view <id> [--json <fields>]` command to display detailed information about a specific pull request.
64
60
- [ ] Use `com.atproto.repo.getRecord` for the `sh.tangled.repo.pull` record.
65
61
- [ ] Fetch associated comments using `com.atproto.repo.listRecords` with `collection: "sh.tangled.repo.pull.comment"`.
62
+
- [ ] Dogfood the CLI by using it to create a pull request for these changes, and then view the created PR to ensure all data is correctly stored and retrieved.
66
63
67
64
### Phase 2: Working as a Reviewer (Commenting)
68
65
···
75
72
### Phase 3: Responding to a Review (Author Workflow)
76
73
77
74
- [ ] This phase primarily involves local Git operations (pushing new commits) and using `tangled pr comment` for clarifications, which are covered by existing or planned commands.
75
+
76
+
## Repository Management
77
+
78
+
- [ ] Implement `tangled repo create <repo-name>` command.
79
+
- [ ] Implement `tangled repo view` command (display repo details).
80
+
- [ ] Support `--json` output with field filtering (e.g., `--json name,cloneUrl,description`) using `lodash/pick`).
78
81
79
82
## SSH Key Upload & Management (Phase 4)
80
83