Claude Skills by ulises-jeremias

Git and developer workflow integration. TRIGGERS: 'generate branch name', 'create branch name', 'branch name for', 'write PR description', 'PR description for', 'link PR', 'link pull request', 'parse commit', 'extract issue from commit', 'smart commit', 'development panel'. Use for Git, GitHub, GitLab, Bitbucket integration with JIRA. NOT FOR: issue field updates (use jira-issue), searching issues (use jira-search), status transitions (use jira-lifecycle).

Core JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile), transitions/status changes (use jira-lifecycle), comments/attachments (use jira-collaborate), time tracking (use jira-time), bulk operations on 10+ issues (use jira-bulk), dependencies/block...

Issue linking, blockers, and dependency analysis. TRIGGERS: 'what's blocking', 'what is blocking', 'is blocked by', 'link issues', 'link to', 'blockers for', 'depends on', 'clone issue', 'clone with', 'blocking chain', 'dependency graph', 'show dependencies', 'get blockers', 'relates to', 'duplicates'. Use for issue dependencies, relationships, and cloning. NOT FOR: epic linking (use jira-agile), field updates (use jira-issue), bulk cloning (use jira-bulk).

Manage issue lifecycle through workflow transitions and status changes. Control who does what and when via assignments, versions, and components.

JIRA cache and performance operations. TRIGGERS: 'warm the cache', 'warm cache', 'cache status', 'clear cache', 'cache warm', 'cache for project', 'discover project', 'project discovery', 'cache hit rate', 'optimize performance', 'rate limit'. Use for JIRA API performance optimization and project context discovery. NOT FOR: project configuration/settings (use jira-admin), issue operations (use jira-issue), bulk issue modifications (use jira-bulk).

Find issues by criteria (status, assignee, priority, etc.) using JQL. Create filters, export results to CSV/JSON, bulk update. Ideal for reporting and automation.

Complete ITSM/ITIL workflow support for JSM - service desks, requests, SLAs, customers, approvals, knowledge base. Use when managing service desk requests, tracking SLAs, or handling customer operations.

Time tracking, worklogs, and time reports. TRIGGERS: 'log time', 'time spent on', 'log hours', 'log work', 'worklog', 'time tracking', 'timesheet', 'how much time', 'time logged', 'time report', 'export timesheet', 'set estimate', 'remaining estimate', 'original estimate'. Use for time-related queries and operations on issues. NOT FOR: SLA tracking (use jira-jsm), date-based issue searches (use jira-search), issue field updates unrelated to time (use jira-issue).

Manage Linear issues, projects and cycles via the Linear MCP server. Use when the user wants

Configure and manage MCP providers for Agent Toolkit — setup, list, doctor, and per-tool

Interact with Slack workspaces for reading channels/messages, sending messages, adding reactions,

Interact with the official Slack CLI to create, run, deploy, and manage Slack apps, environments,

Execute and manage loop engineering primitives (init, run, status, audit) from an AI coding

'WHAT — Generate or update documentation from code: README.md from repo structure, CHANGELOG.md

WHAT — Recommend the most cost-effective LLM provider for a given task type. Shows estimated

Create artifact/commit file handoffs for Agent Toolkit swarms with worktree-per-writer, branch,

Observe, diagnose, and recover Agent Toolkit swarm runs via status, handoffs, logs, and attach

Launch an Agent Toolkit swarm from a natural language request using agent-toolkit swarm CLI

Workstation health triage — validate tooling, directory layout, and run doctor with remediation

Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.

CodeQL operational workflow — discover/config, run/inspect, triage SARIF findings (rule/query ID, source→sink, evidence), remediate, re-validate. Distinguishes broad MegaLinter linting from semantic security analysis.

Evidence-based deep code review rubric — severity + confidence findings across maintainability, correctness, security, performance, and testing. Push for ambitious structural simplification (code judo), not just local cleanup. Escalate hands-on triage to the code-reviewer agent.

Remove AI-generated code slop and clean up code style

Collect MegaLinter lint errors for the current repository. Use when the user wants to know

Fix the errors reported by MegaLinter. Use after megalinter-check found errors, or when the

Install or upgrade MegaLinter on a repository. Use when the user wants to add MegaLinter

Entry point for everything MegaLinter. Use when the user wants to lint their repository,

Cut AI tells from any writing. Must always apply.

Use Chrome DevTools MCP to control and inspect a live Chrome instance for network, console, performance, rendering, and Deep debugging. Pairs with playwright-cli (deterministic interaction/E2E) — complements, not duplicates.

Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples, stdin/pipelines, fast actionable errors, idempotency, dry-run, and predictable structure. Use when building a CLI, adding commands, writing --help, or when the user mentions agents, terminals, or automation-friendly CLIs.

Manage Herdr workspaces, tabs, and panes for Agent Toolkit swarms with eager windows, shell-aware

Discover installed skills, agents, loops, and platform capabilities via agent-toolkit inventory,

Create, scaffold, or refactor Jupyter notebooks (.ipynb) for experiments and tutorials. Prefer

WHAT — Mermaid diagrams from text (flowchart, sequence, class, state, ER, gantt, gitGraph) — Markdown-native, Git-native, MIT. Primary renderer for architecture pack; renders via GitHub native or mermaid CLI (mmdc) to SVG/PNG.

Drive a real browser from the terminal using the Playwright CLI (snapshot, click, fill, screenshots,

A minimal test skill for golden snapshot testing.