@intentic/claude-plugin
Reduces context setup time and token waste by automatically surfacing project structure, trimmed logs, and session stats—letting teams focus on code problems…
The intentic Claude Code plugin: trimmed Bash output, a project map and field notes at session start, iq search and fileq teaching, and a /intentic:stats report of what each saved
- Generate a project map automatically when starting a Claude session to understand codebase structure quickly
- Search across saved files and field notes using iq search to find relevant code patterns and documentation
- Ask Claude to produce a stats report showing usage metrics and what each saved file contributes to your project
Reduces context setup time and token waste by automatically surfacing project structure, trimmed logs, and session stats—letting teams focus on code problems instead of file hunting and prompt engineering.
Engineering teams using Claude for codebase navigation, debugging, and architectural analysis in large projects.
https://www.npmjs.com/package/@intentic/claude-plugin
By GitHub Actions
How to Get It
npx @intentic/claude-plugin
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me generate a project map automatically when starting a Claude session to understand codebase structure quickly
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 53 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 53 GitHub stars; contributors unknown; last commit 0d ago; license MIT.