doctorspider42

Code map and conventions of the Jira Auto Logger Electron app - process layers, typed IPC contract, domain model, LLM pipeline, config migrations, i18n and theming rules. Use this before adding any feature, changing the config shape, adding an IPC channel, touching the LLM prompt, or modifying Jira/Tempo integration - it contains the checklists that keep changes consistent.

How to release Jira Auto Logger - version bumping, tagging, the GitHub Actions release workflow, built binaries and CI troubleshooting. Use this whenever the user asks to release, publish, ship a version, build installers, check why CI failed, or modify the GitHub workflow.

How to run, debug and manually test the Jira Auto Logger Electron app - dev mode, mock mode with fake data, screenshot automation, diagnostic logs and config locations. Use this whenever you need to start the app, reproduce a bug, verify a UI change, work without real Jira/Tempo credentials, or regenerate the README screenshots.

Smoke-test the project-shared-memory MCP server. Use when testing, validating, or verifying the project-shared-memory MCP. Runs a full CRUD lifecycle across all scopes (user, repo, session): connectivity check, create, read, update (str_replace), insert, rename, delete — with verification after every mutation.

Use when a user asks to create, scaffold, bootstrap, or wire up a new MCP server in a repository. Best for local stdio servers that should usually live under .github/mcp/<mcpname>, run via npx from the project, and be added to .vscode/mcp.json.