-
I don't use org clocking. I rarely use the archive feature. Only when switching jobs, I move my old business file content to an archive file. I like to find all business-relevant information when searching through one single Orgdown file. If I'd split up done tasks/sub-projects/whatever to archive files, I'd lose tha ability to find older stuff by chance when I've forgotten that, e.g., I already worked on this particular Jira ticket two years ago.
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
I am the author of org-gtd -- which /u/reddit_clone indicated they were using. It is, as they said, quite opinionated -- I am _trying_ to capture the workflow as described by the GTD book, but it is limited by my understanding of org-mode, org-agenda, and elisp.
-
rofi-org-todo
A rofi script to allow easy hotkey CAPTURE of org-mode TODOs to an emacs inbox.org file for later processing.
I leave the todos in the daily files (in org super-agenda it gives them context) and then generally have org-roam links if they are related to a project and the person and then use tags like :perso: or :work: and usually a week if they are not scheduled (eg. :w49:), so they are separable in the agenda. This helps me focus on things that are important (also, you can tab to collapse or expand section using origami in super-agenda which helps to focus or not. I do have an inbox.org file for capture (and one called inbox13.org for my mobile device separately since I've had conflicts on Dropbox and iCloud before) though this is more to get stuff out of my head quickly (I'm the author of rofi-org-todo https://github.com/wakatara/rofi-org-todo ) and then I just process the inbox a la Dave Allen and usually put them with context notes in the daily file.
