FarzamMohammadi

commit

Analyze code changes, group them into logical packages where appropriate, to create sequential, clear, descriptive commits with effective titles and detailed descriptions

Author a comprehensive, reviewer-ready pull request or GitLab merge request description from the current branch's changes and the working session's context, saved to an isolated temp file. Use this whenever someone is wrapping up a piece of work and needs the writeup — phrasings like "write the PR description", "draft the PR/MR", "create a pull request description", "describe these changes for review", or finishing a branch before opening a merge request. The skill's edge is that it carries the reasoning the diff can't show — why this approach, the root cause behind a bug, the decisions and rejected alternatives, scope and follow-ups, related tickets, and how this PR fits a multi-PR effort.

skill-creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Data & Documents Listed

md-to-confluence

Upload a Markdown (.md) file to a Confluence Cloud page with tables, headings, formatting, and mermaid diagrams all rendering correctly — no copy-paste, no wording changes. Use this whenever someone wants to publish, push, sync, or upload a markdown doc, spec, design, or README to Confluence, or complains that pasting markdown into Confluence breaks the tables or diagrams. Also trigger on "put this doc on Confluence", "get this on the wiki", "publish this to Confluence", or updating an existing Confluence page from a markdown source.

workflow-orchestrator

Take on a substantial, multi-step effort as a strategic orchestrator — intake the goal, research and plan it solo, execute it through parallel/sequential agent workflows, then personally verify the result end to end. Use this whenever the user wants to tackle something big or ambitious: a large feature, a cross-cutting refactor, a migration, a codebase-wide audit, a "do all of X / sync everything / overhaul Y" task, or any effort that won't fit in one pass and needs to be planned and orchestrated with rigor. Trigger when the user invokes it by name, says things like "orchestrate this / run a workflow / use subagents / plan and build this / take this on end to end," OR simply describes a meaty multi-part task and wants it done thoroughly and efficiently — even if they never say the words "workflow" or "orchestrate." Do NOT use it for small, single-step tasks that one pass handles directly.