chatcrystal-debug-recall
Recall Historical Debugging Solutions
Stop reinventing the wheel when debugging. This skill recalls historical fixes and root causes from your ChatCrystal memory, helping you diagnose failing tests, compiler errors, and runtime exceptions faster by leveraging past debugging sessions.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "chatcrystal-debug-recall". Use $chatcrystal-debug-recall to find similar TypeScript TS2322 errors we have fixed before.
Expected outcome:
Recalling from ChatCrystal memory... Found 3 relevant debugging sessions: 1) 'TS2322 error in src/api/auth.ts caused by missing generic type parameter on API response wrapper - fixed by adding type annotation', 2) 'TS2322 in user model due to union type incompatibility - resolved by using intersection type', 3) 'TS2322 when upgrading from TS 4.9 to 5.0 - caused by stricter type inference on conditional types, fixed by adding explicit type casts.
Using "chatcrystal-debug-recall". Use $chatcrystal-debug-recall with this error: NullPointerException at UserService.getProfile(UserService.java:42). Project: /myapp, Branch: main.
Expected outcome:
Found 2 relevant memories: 1) 'NPE at UserService.getProfile line 42 occurred when database connection pool was exhausted - fix was to increase pool size and add connection validation', 2) 'Same NPE location happened when user cache was not initialized on cold start - fixed by adding @PostConstruct initialization method'. Both memories suggest checking database connectivity and cache initialization.
Security Audit
SafeAll 21 static findings are false positives from markdown code blocks. The skill contains only documentation and an agent configuration file with no executable code, network operations, or security risks. The detected 'external_commands' patterns are markdown backtick syntax for JSON examples, not shell execution. The 'weak cryptographic algorithm' flags are false positives from documentation strings.
Low Risk Issues (1)
Quality Score
What You Can Build
Debug Test Failures After Dependency Upgrade
Developer encounters failing tests after upgrading TypeScript from 4.9 to 5.2. The skill recalls previous debugging sessions where similar type errors occurred and identifies the root cause as changed type inference in the new TypeScript version, along with the specific fix applied.
Diagnose Runtime Exceptions in Production
DevOps engineer sees recurring NullReferenceException in production logs. The skill retrieves historical debugging sessions showing this exception occurs when the configuration cache is stale, with the exact fix to invalidate cache after config updates.
Resolve Build Breakage After Merge
Developer's build breaks after merging a feature branch with compiler errors about missing dependencies. The skill recalls a previous session where the same issue occurred and identifies that the merge strategy dropped a submodule reference, providing the fix command.
Try These Prompts
Use $chatcrystal-debug-recall to find similar errors we have fixed before.
Use $chatcrystal-debug-recall with this error: [paste error message and stack trace]. The project directory is /path/to/project and the branch is feature/new-auth.
Use $chatcrystal-debug-recall to find previous TypeScript upgrade issues. Error signature: TS2322 'Type is not assignable to type'. Affected files: src/types/user.ts and src/api/auth.ts.
Use $chatcrystal-debug-recall to investigate this performance regression: API response time increased from 50ms to 500ms after the database migration commit. Check for similar performance issues we have debugged before.
Best Practices
- Always provide error signatures like exception types, error codes, and log signatures when available to improve memory recall precision
- Include project directory, branch, and affected file paths to help prioritize project-specific memories over global ones
- Use recalled memories to inform your diagnosis but always verify the root cause in the current environment before applying fixes
- Combine this skill with manual debugging steps rather than relying solely on historical solutions
Avoid
- Applying recalled fixes without verifying they match the current error signature and environment context
- Overfitting to a historical solution when the current failure has materially different symptoms or stack traces
- Fabricating historical debugging data when ChatCrystal Core or MCP tools are unavailable in degraded mode
- Calling the skill for non-debugging tasks like feature development or refactoring without clear error contexts