chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
What this skill does
# ChatCrystal Debug Recall
Use this skill when the task is clearly about diagnosis or debugging. Keep the skill thin and let ChatCrystal Core handle retrieval.
## Workflow
1. Trigger when the task includes failing tests, compiler errors, runtime exceptions, broken dependencies, environment problems, or performance regressions.
2. If `recall_for_task` is available, call it before proposing a fix with:
- `mode: "debug"`
- `task.goal`: the concrete debugging objective
- `task.task_kind: "debug"`
- `task.project_dir` and `task.cwd` when known
- `task.branch` when known
- `task.related_files` or `task.files_touched` when known
- `task.error_signatures` populated with the most useful identifiers available
3. Prefer concrete signals such as:
- failing test names
- exception classes
- error codes
- log signatures
- package or tool versions when they materially affect the failure
4. Prioritize returned memories that explain root cause, remediation, or known pitfalls.
5. Use recalled memories to sharpen diagnosis, not to skip verification in the current environment.
## Example MCP Input
Use this shape when calling `recall_for_task` for debugging:
```json
{
"mode": "debug",
"task": {
"goal": "Diagnose failing build after TypeScript upgrade",
"task_kind": "debug",
"project_dir": "/path/to/project",
"cwd": "/path/to/project",
"branch": "upgrade/typescript",
"related_files": [
"server/src/cli/mcp/server.ts",
"tsconfig.base.json"
],
"error_signatures": [
"TS2322",
"Type is not assignable"
],
"source_agent": "codex"
},
"options": {
"project_limit": 5,
"global_limit": 3,
"include_relations": true
}
}
```
## Full Mode
Full mode requires ChatCrystal Core plus MCP access to `recall_for_task`.
- Keep `project_memories` primary and `global_memories` secondary.
- If the response includes warnings or `no-matches`, continue debugging normally.
- Do not overfit to a recalled fix when the current failure signature diverges materially.
## Degraded Mode
If ChatCrystal Core or the MCP tool is unavailable:
- Continue the debugging task without blocking.
- State briefly that long-term debug recall is unavailable.
- Do not fabricate historical failures, causes, or fixes.
- Do not turn installation commands into automatic skill steps.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.