Creates a Remote Hands ticket for datacenter on-call staff to check a server and boot it into the OS; status and replies appear in the ticket link emailed to you.
Produce a ticket-ready remediation payload for a chokepoint, containing summary, justification, change plan, and rollback note for direct paste into Jira or ServiceNow.
A 4-stage reading companion that helps users set reading goals, discover books, track progress, and deepen learning through reflection, integrated with Claude Desktop.
Enables document conversion between PDF, DOCX, and Markdown formats to facilitate reading and editing complex files in AI tools like Claude Desktop or Cursor. It utilizes marker-pdf and pandoc to provide structured text versions of documents, helping to manage context and support unsupported file types.
Creates the primer/ ticket store and adds workflow instructions to CLAUDE.md; accepts an optional Jira key for later exports. Call once per project before other tools.
Resolve a Jira ticket, create a local branch with auto-generated name, fetch project README from Bitbucket for conventions, and get a next-steps summary. Use issue key or free-text search.
Record investigation steps, evidence, findings, or remediation actions directly on a Jira ticket. Preserves the audit trail of security incident responses.
Retrieve a specific Jira ticket comment by ticket key and comment ID, with optional embedded images, when only that comment is needed instead of the whole ticket.
Lists folders in a Postman collection, showing name, ID, path, and request count. Verify a folder exists for a Jira ticket before running its requests.
Retrieve full details of a Jira ticket by key, optionally including comments, worklogs, and image attachments. Use it to inspect a single issue before acting or updating.
Retrieves and consolidates Jira ticket requirements, comments, architecture docs, and coding standards. Call this first when starting work on a ticket.
Create a git worktree for a ticket or feature, giving you an isolated directory for parallel work without switching branches. Name the branch automatically from a ticket ID.
Retrieve all available Jira fields with their metadata and field IDs for a specific ticket or project. The returned mapping enables accurate field updates.