proc-janitor / integrations
AGENTS.md7 starsChanged 9 months agoMITView on GitHub
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- resources/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- src/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- analyzeSkill
The file
We found no rules to list in this file: it reads as prose or reference rather than instructions.
Files
<!-- Parent: ../AGENTS.md --><!-- Generated: 2026-02-06 -->integrations
Purpose
Integration helpers for connecting proc-janitor with editors, shells, and tools.
Key Files
| File | Description |
claude-code-setup.sh | Setup script for Claude Code integration (auto-registers sessions) |
shell-integration.sh | Shell hooks for automatic session tracking on terminal open/close |
vscode-tasks.json | VS Code tasks for scan, clean, and status commands |
For AI Agents
Working In This Directory
- These are optional convenience scripts, not required for core functionality
shell-integration.shis sourced from.bashrc/.zshrcvscode-tasks.jsonis copied to.vscode/tasks.jsonin user projects
<!-- MANUAL: -->Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

