This Claude Code plugin is part of my public marketplace.
To install the marketplace:
/plugin marketplace add https://github.com/danielrosehill/Claude-Code-PluginsPlugin Installation:
To install this plugin:
/plugin install fix-documentation@danielrosehillA Claude Code plugin for documenting system administration fixes and changes across multiple platforms (Notion, Obsidian, Email).
System administration with Claude Code is powerful, but those terminal outputs documenting what changed aren't suitable for long-term retention. Claude Fix Logger solves this by providing commands and agents to automatically capture comprehensive fix documentation across your preferred platforms.
- Multiple Documentation Platforms: Save to Notion, Obsidian, or email
- Intelligent Agent: Orchestrates documentation across platforms based on your preference
- Structured Templates: Consistent formatting for problem/solution documentation
- Cross-Platform References: Links between Notion, Obsidian, and email for comprehensive trails
- MCP Integration: Leverages Notion, Resend, and Time MCPs for seamless automation
Available via Daniel's Claude Code Plugins Marketplace.
Creates a detailed logbook entry in Notion using the Notion MCP.
Usage:
/save-to-notion
Requirements:
- Notion MCP configured
- Time MCP (optional, for accurate timestamps)
What it does:
- Gets current date/time
- Formats fix documentation with problem/solution structure
- Creates page in your Notion workspace
- Confirms successful creation
Documents changes in an Obsidian notebook and pushes to GitHub.
Usage:
/save-to-obsidian
Configuration:
Update the path in commands/save-to-obsidian.md to match your Obsidian notebook location (default: /home/daniel/obsidian-notebooks/notes-from-ai).
What it does:
- Creates markdown note in your Obsidian vault
- Organizes into logical subfolders (e.g., "GPU-Fixes")
- Pushes notebook to GitHub
- Provides file path confirmation
Sends comprehensive email summary via Resend MCP.
Usage:
/email-me-the-fix
Requirements:
- Resend MCP configured
Configuration: Update recipient and sender addresses in commands/email-me-the-fix.md.
What it does:
- Formats fix documentation in clean HTML
- Includes references to Notion/Obsidian docs if created
- Sends to dedicated email (e.g.,
[email protected]) - Provides confirmation of send
Pro Tip: Use a dedicated email address like [email protected] to organize all AI-generated fix documentation in a single email folder/tag.
An intelligent agent that orchestrates documentation across multiple platforms based on your preference.
How to invoke: Claude Code will automatically suggest this agent when you complete a system fix, or you can explicitly invoke it:
Please document this fix
What it does:
- Analyzes the conversation to understand the fix applied
- Asks which platform(s) you prefer (Notion, Obsidian, Email, or all)
- Executes the appropriate slash commands in sequence
- Includes cross-references when using multiple platforms
- Confirms completion with summary of what was documented
Example interaction:
User: "Great, that fixed the GPU driver issue!"
Agent: "Excellent! Where would you like me to document this GPU driver fix?
Options:
1. Notion - Structured page in your Notion workspace
2. Obsidian - Markdown note in your 'Notes From AI' notebook
3. Email - Summary sent to your email
4. All three - Complete documentation trail
What's your preference?"
User: "All three please"
Agent: [Executes /save-to-notion, /save-to-obsidian, /email-me-the-fix]
This plugin works best with the following MCPs configured:
| MCP | Required For | Optional? |
|---|---|---|
| Notion | /save-to-notion command |
Yes |
| Resend | /email-me-the-fix command |
Yes |
| Time | Accurate timestamps | Yes |
All MCPs are optional - commands that require unavailable MCPs simply won't function.
Obsidian Notebook: Edit commands/save-to-obsidian.md line 7:
/home/your-username/obsidian-notebooks/your-notebook-nameEmail Recipients: Edit commands/email-me-the-fix.md lines 7-12 to update sender/recipient addresses.
All commands follow this consistent structure:
# Fix Title
## Problem
Summarize the problem that was resolved or what was optimized.
## Fix
Summarize the fix/remediation/optimization.
If several failed approaches were tried first, note them only if
that information might be significant in the future. Otherwise,
just document what worked.Formatting Guidelines:
- Code blocks in fenced code blocks
- Clear headings and subheadings
- Professional but concise tone
- Includes metadata (date, time, verification)
# Just fixed something, save to Obsidian
/save-to-obsidian# Important fix, document everywhere
/save-to-notion
/save-to-obsidian
/email-me-the-fixUser: "Fixed the kernel panic issue!"
User: "Please document this"
# Agent asks preference and handles the workflowclaude-fix-logger/
├── .claude-plugin/
│ └── plugin.json # Plugin manifest
├── commands/
│ ├── save-to-notion.md # Notion documentation command
│ ├── save-to-obsidian.md # Obsidian documentation command
│ └── email-me-the-fix.md # Email summary command
├── agents/
│ └── fix-documenter.md # Orchestration agent
├── LICENSE
├── CHANGELOG.md
└── README.md
When using Claude Code for system administration, documenting changes is crucial for:
- Accountability: Know exactly what was changed and when
- Learning: Build a personal knowledge base of solutions
- Recovery: Quickly understand and reverse changes if needed
- Team Sharing: Communicate fixes to team members
- Compliance: Maintain audit trails for regulated environments
Without external tooling, terminal outputs are ephemeral. This plugin ensures your hard-won solutions are captured and organized.
After resolving a GPU driver issue, run /save-to-obsidian to create:
# AMD ROCm Driver Fix - 2025-11-16
## Problem
ROCm was failing to detect GPU after kernel update to 6.14.0-15
## Fix
Reinstalled ROCm with proper kernel headers:
```bash
sudo apt install linux-headers-$(uname -r)
sudo apt reinstall rocm-dkms
sudo rebootVerification: rocm-smi now shows GPU properly
### Networking Issue Trail
For a complex networking fix, use the agent to document across all platforms:
- Notion: Detailed technical reference with diagrams
- Obsidian: Quick reference in "Network-Fixes" folder
- Email: Summary with links to both for easy access
---
## Contributing
Contributions welcome! Please feel free to submit issues or pull requests.
### Development
1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Test with Claude Code
5. Submit a pull request
---
## License
MIT License - see [LICENSE](LICENSE) for details.
---
## Author
**Daniel Rosehill**
- Website: [danielrosehill.com](https://danielrosehill.com)
- Email: [email protected]
- GitHub: [@danielrosehill](https://github.com/danielrosehill)
---
## Related Projects
- [Claude Code Repos Index](https://github.com/danielrosehill/Claude-Code-Repos-Index) - My other Claude Code projects
- [GitHub Master Index](https://github.com/danielrosehill/Github-Master-Index) - All my GitHub repositories
---
## Changelog
See [CHANGELOG.md](CHANGELOG.md) for version history and updates.