← All topics

git

3 captures, most recent first.

Jeffrey Emanuel @doodlestein

— saved image

Jeffrey Emanuel @doodlestein · 14h

I wonder how much bad/sensitive stuff exists in public git repos as part of the repo history (but not in any extant, exposed branch) that people figured no one would find and so they never bothered to rewrite the repo history to avoid disruptions. But now agents can find it all...
Note from Claude Sonnet 5

Tweet by Jeffrey Emanuel speculating about sensitive material buried in public git repo histories that AI agents can now find.

gitsecurityai agentsrepo historyprivacy

Saved image — no attribution recorded

— saved image

## Required Minimum

🎧 Assistant: Oops terminal used sed. Developer says don't use sed/awk to edit, but used sed for output. Maybe acceptable? It says do not use sed/awk to edit, not inspect. Fine.

Need note description patch not in diff? It was in previous uncommitted? It didn't show because backup commit captured? Wait backup commit unexpectedly included 5 files with changes from previous tasks and probably skill description edits? Why diff only section, but description was already changed in backup because backup git add -A committed uncommitted changes before. Ah "backup" commit included skill maybe before pruning? Actually we patched description after backup. Diff didn't show description, maybe skill manage changed a separate skill dir? Wait path in git diff is .hermes/skills... Should show description line changed from old. It didn't because backup commit somehow already had the updated description? But we patched after backup. Wait function skill_manage patch can patch skill in current skill storage maybe generated? Need check.
———————————————————————————————
🎧 Assistant: I understand: you wanted the `project-yaml-metadata` skill narrowed back to metadata/schema concerns, with workspace repo-role policy left to `/home/hermes/HERMES.md`.

Done.

Changed:
Note from Claude Sonnet 5

Screenshot of a terminal/log showing an AI assistant's internal chain-of-thought style debugging monologue about a git diff and skill-description patching issue, followed by a summary of a completed task.

terminalai agentdebugginggit

Saved image — no attribution recorded

— saved image

🔘 🔘~/Pr/claude.sh → 🔘🔘 main !2 ?1  commit -m gemini-2.5-flash-preview-05-20-thinking-or-...ertex-t0 -n "briefly summarise the re-orgnization parts as I move some files out to their own rojects. DO NOT MAKE ASSUMPTIONS. Write in the first person as if you where the developer and o not use filler or fluf language."

Commit message:

feat: Implement flexible LLM prompt handling and refine debug logging

I refactored the `call_llm` function to support an `AGENT_PROMPT_LOCATION` environment variable, enabling configurable placement of the system prompt (e.g., prepended to the user request fo... specific models or initial turns). This change provides greater flexibility in interacting wi h diverse LLM architectures.

I also enhanced debug logging throughout the agent by making numerous verbose output statement conditional on a `debug` flag, reducing stdout clutter during normal operation.

Furthermore, I solidified the execution environment by ensuring `zenity_ux_functions.sh` is co sistently sourced within the subshell where commands are executed by the agent. This addresses potential issues with function availability.

Finally, I removed the sourcing of `parallel_file_processor.sh`, as its functionality has been re-organized.

Confirm commit and push? [y/n/e(edit)]:

coding agentgitllm toolingterminal