FarzamMohammadi
- 30 skills
- 0 followers
- 4 hours ago last updated
- ▌ Excalidraw · farzammohammadi bundleGenerate .excalidraw JSON files for architecture flows, system diagrams, and simple sketches from natural-language descriptions. Use whenever the user asks to draw, sketch, diagram, or visualize a flow, architecture, pipeline, or system with a small number of boxes (up to ~15) — especially for slides, docs, or when they mention excalidraw. Also trigger when the user describes components and their connections ("X calls Y which writes to Z") and wants something they can open in excalidraw.com.
- ▌
- ▌
- ▌ Review · farzammohammadi bundleConducts post-implementation review covering test coverage, lint, type checks, test fixes, and local testing preparation. Runs all automated verification, identifies gaps, fixes issues, and presents a testing checklist so the user can verify the work manually. Use this skill after implementation and commits are done — as the final quality gate before creating an MR. Also use when the user says "review this", "check my work", "run the checks", "verify everything", "is this ready", or "final review". Pairs with /commit (before) and /glab-mr-manager (after).
- ▌ Wrap Session · farzammohammadi bundleWrap up a session by capturing context, decisions, and state into project-native documentation, then generate a continuation prompt for the next chat. Use when ending a session, switching context, or preparing a handoff.
- ▌ Improve Skill · farzammohammadi bundleReflect on a skill's performance and iterate on improvements. Use after running any skill to identify gaps and refine it.
- ▌ Refactor Code · farzammohammadi bundleReview git diffs against comprehensive refactoring principles. Use when user wants code review, refactoring suggestions, or mentions reviewing changes.
- ▌ Resume Builder · farzammohammadi bundleCollaborative, puzzle-piece-based approach to refining resumes, LinkedIn bios, and professional content. Use this skill whenever the user wants to improve, refine, polish, rewrite, tighten, or workshop any resume content (summaries, bullet points, experience sections, headlines), LinkedIn bios or about sections, cover letters, or any professional self-presentation writing. Also trigger when users share resume text and ask for feedback, want to make wordy bullets more concise, are preparing job application materials, or ask to 'make this sound better' for professional contexts. Trigger even for partial requests like 'help with this bullet' or 'does this summary work?'
- ▌ Commit · farzammohammadiAnalyze code changes, group them into logical packages where appropriate, to create sequential, clear, descriptive commits with effective titles and detailed descriptions
- ▌ Gws · farzammohammadi bundleUnified interface for Google Workspace via the gws CLI. Send Gmail, create/read/append Google Docs and Sheets, upload and share Google Drive files, and convert markdown to formatted Docs. Use when the user mentions Gmail, Google Docs, Google Sheets, Google Drive, or Google Workspace tasks.
- ▌ Commit 2 · farzammohammadi bundleAnalyze code changes, group them into logical packages where appropriate, to create sequential, clear, descriptive commits with effective titles and detailed descriptions
- ▌
- ▌ Review Pr · farzammohammadi bundleFind bugs in branch changes — races, logic errors, security holes, contract mismatches. Use when user wants to review a PR or branch.
- ▌ Summarize · farzammohammadi bundleDistill files, URLs, and videos into thorough summaries that preserve every valuable detail while cutting fluff. Use when user wants to summarize, get a tl;dr, extract key takeaways, digest, break down, or understand the main points of any content — even if they just say "what does this say" or paste a link.
- ▌ Research · farzammohammadi bundleInvestigates codebases with a facts-before-opinions discipline — building a complete factual picture before interpreting what it means for the work ahead. Produces a structured research document saved to disk, split into observations and implications. Use when you need to understand existing code, patterns, dependencies, and constraints. Also use when the user says "research this", "explore the codebase", "investigate", "what does this code do", or "understand the system".
- ▌ Glab Mr Manager · farzammohammadi bundleManage GitLab Merge Requests - create, review, approve, merge, and full MR lifecycle
- ▌ Literary Editor · farzammohammadi bundleTransform drafts into polished English. Use when refining any written content—notes, messages, articles, documentation.
- ▌ Implement · farzammohammadi bundleExecutes an approved plan by ALWAYS orchestrating the build through focused agent workflows, then taking the role of orchestrator and co-owner to independently verify every change, hunt gaps, and fix whatever was missed until the work is fully home — no gaps, bugs, or loose ends. This is the "I" (Implement) of RRPIR: it runs after create-plan and before the optional review. Use this skill whenever it's time to build, implement, or execute an approved plan — when the user says "implement this", "build it", "execute the plan", "do the work", "make it happen", or "let's build it", and especially right after a plan has been approved. Reach for it for any multi-step implementation rather than hand-coding everything inline. Note: verification here means confirming the orchestrated build delivered the plan without gaps — it does NOT run the separate /review quality gate (coverage analysis, bug-hunt, MR prep), which the user runs on their own afterward.
- ▌ Finalize Changes · farzammohammadi bundleHolistic review of completed work to elevate quality from good to excellent. Use after implementation is done to catch what was missed.
- ▌ Md To Confluence · farzammohammadi bundleUpload 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.
- ▌ Create Plan · farzammohammadi bundleSynthesizes requirements and research into robust implementation plans through structured decision-making and expert panel stress-testing. Calibrates process depth to risk level — low stakes get a light plan, full stakes get hard decision gates and a pre-mortem. The plan is a decision record with actionable tasks, not an execution script. Use when you need to turn accumulated findings into a plan with clear choices, sequenced tasks, and verification. Also use when the user says "plan this", "create a plan", "how should we implement this", "design the approach", or "what's the strategy".
- ▌ Demo Video Creator · farzammohammadi bundleProduce a dope, almost-professional, deterministic-yet-REAL automated product-demo video of a software system — real surfaces, real footage at true 4K/8K, the AI/LLM as the only stubbed piece, polished in Remotion. Use this whenever the goal is a marketing/launch/portfolio demo film of a running product (a CLI, agent, web app, pipeline) that must SHOW the real system working end-to-end, reproducibly, at the highest quality — not a slide deck, not a screen-recording, not a mockup. Covers the full pipeline: harness architecture, 8K browser capture (never recordVideo), Remotion polish, and the orchestrate-and-verify discipline. Heavy and side-effecting — invoke it deliberately.
- ▌ Repo Docs Overhaul · farzammohammadi bundleOverhaul a repository's documentation layer for clarity and navigability. Rewrites root README, creates section READMEs, renames vague files, adds contributor guides, and codifies documentation conventions. Use when a repo needs to be made OSS-ready or its docs feel generic/sparse.
- ▌ Expert Panel Review · farzammohammadi bundleRun code, architecture, systems, or proposed changes through a panel of world-class engineering perspectives. Each panelist reads the ACTUAL source files before judging. Use this skill whenever the user asks to: review code quality, get expert opinions, assess architecture decisions, evaluate a refactor plan, critique a design, run something 'through expert eyes', get a 'Linus review', assess quality against the best projects, compare to top OSS standards, or get unbiased multi-perspective feedback. Also trigger for: 'what would X think of this', 'is this good enough', 'how does this compare to the best', 'give me honest feedback', 'tear this apart', 'brutal review', 'no-bullshit assessment'. This is for EVALUATING existing code or proposals — not for writing new code or extracting system structure (use system-layer-extraction for that).
- ▌ Jira Ticket Manager · farzammohammadi bundleManage Jira tickets - create, search, update, comment, and transition issues
- ▌ Modularize Document · farzammohammadi bundleTransform monolithic markdown into modular index + detail files. Use when user wants to split large documents or mentions modularizing.
- ▌ Create Pr Description · farzammohammadiAuthor 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.
- ▌ Workflow Orchestrator · farzammohammadiTake 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.
- ▌ System Layer Extraction · farzammohammadi bundleDeep architectural investigation that extracts, documents, and maps every system in a codebase. Use this skill whenever the user asks to: extract layers, map systems, analyze architecture, investigate codebase structure, document system boundaries, create a system map, understand how systems relate, audit dependencies, assess isolation, or do any form of comprehensive architectural analysis. Also trigger when the user says things like 'I want to see all the layers', 'map out the systems', 'what are the moving parts', 'how is this structured', or 'give me the full picture of the architecture'. This is NOT for reviewing code quality or individual files — it's for understanding the full system topology.
- ▌ Requirements Gathering · farzammohammadi bundleConducts structured requirements gathering through sequential questioning before any research, planning, or implementation begins. Extracts true intent, constraints, edge cases, unknowns, and acceptance criteria from the user through focused one-at-a-time questions. Use this skill whenever the user mentions a new feature, task, ticket, bug fix, or any work item that hasn't been fully scoped yet. Also use when the user says "let's start", "new task", "I need to build", "requirements", "scope this", or "grill me" — even if they jump straight to implementation, redirect to requirements first.