Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

mohammaddaoudfarooqi

@mohammaddaoudfarooqi source repo

5 published skills

  1. ▌
    Doc Authoring · mohammaddaoudfarooqi bundle
    Documentation authoring for AI coding agents. Analyzes a repo and generates docs classified by Diataxis type (tutorial, how-to, reference, explanation), kept synchronized with the code. Handles greenfield, brownfield (refresh, enhance, rewrite), and doc audits. Use when the user requests project documentation: a README, API reference, architecture doc, developer guide, contributing guide, changelog, ADR, or onboarding doc, or when existing docs need an audit, refresh, or restructure. Triggers on phrases like "write a README", "document this project", "API reference", "developer guide", "audit our docs", or "Diataxis", and when creating or editing `README.md`, `CONTRIBUTING.md`, `CHANGELOG.md`, files under `docs/`, or doc tooling config (`mkdocs.yml`, Docusaurus, Sphinx). Also triggers when a public API, CLI flag, or config option changes and docs must stay in sync. Do NOT use for standalone prose, marketing copy, blog posts, or design documents unrelated to a codebase.
    0
    installs
  2. ▌
    Github Actions · mohammaddaoudfarooqi bundle
    GitHub Actions workflow authoring for AI coding agents. Analyzes a repo's project type, language, and deployment targets, then generates production-grade CI/CD workflows with security hardening, caching, and optimization. Handles greenfield, brownfield, and audits. Use when the user requests GitHub Actions workflows: CI pipelines, CD deployments, release automation, or scheduled jobs, or when existing workflows need auditing, optimizing, or hardening. Triggers on phrases like "set up CI", "add CI/CD", "deploy on tag", "publish to npm/PyPI", "harden this pipeline", "pin actions to SHA", "OIDC", or "audit my workflows", and when creating or editing files under `.github/workflows/`, `action.yml`/`action.yaml`, or `.github/dependabot.yml`. Also triggers when migrating from GitLab CI, CircleCI, Travis, Jenkins, or Drone to GitHub Actions. Do NOT use for non-GitHub CI systems unless migrating TO GitHub Actions, or for general bash scripting, Makefiles, or local build config.
    0
    installs
  3. ▌
    Text Humanizer · mohammaddaoudfarooqi bundle
    Removes signs of AI-generated writing from enterprise text and rewrites it as clear, specific, human-authored prose. Detects and fixes patterns such as significance inflation, marketing language, em-dash overuse, copula avoidance, rule-of-three, AI vocabulary (leverage, robust, delve, seamless), uniform sentence length, false balance, sycophancy, and chatbot artifacts, while preserving technical accuracy and the document's register. Use when asked to humanize, de-AI, naturalize, or polish text, or when writing or editing enterprise docs, design docs, API references, reports, executive summaries, status updates, emails, or blog posts that must not read as AI-generated. To generate documentation from a codebase, use doc-authoring; this skill humanizes prose that already exists. Do NOT use to evade plagiarism or AI-detection systems for deceptive purposes, or to alter the factual content, terminology, or meaning of a document.
    0
    installs
  4. ▌
    Spec Driven Tdd · mohammaddaoudfarooqi bundle
    Spec-driven test-driven development for AI coding agents. Transforms ambiguous requests into verified implementations through structured specs, derived tests, and strict TDD. Verifies on two axes: coverage and realism (smoke tier, mock-parity, boundary inventory, phase-end demo). Handles greenfield, brownfield, refactors, and complex bug fixes. Use when the user requests a new feature, module, refactor, API, CLI tool, or system with multiple requirements, edge cases, or unclear specs, or for complex bug fixes needing root cause analysis. Triggers on phrases like "add a feature", "implement", "refactor", "fix this bug", "write tests for", "TDD", "test-first", "spec this out", or "mock parity", and when modifying code with adjacent test files or test config. Also triggers on mentions of edge cases, invariants, acceptance criteria, or EARS. Do NOT use for one-line fixes, cosmetic changes, formatting, renames, dependency bumps, or tasks already fully specified with tests provided.
    0
    installs
  5. ▌
    Production Readiness · mohammaddaoudfarooqi bundle
    Run an OSS-only production readiness audit of a codebase and emit a Markdown report with file:line citations, severity-ranked findings, a "What's Good" section, and a Go/No-Go verdict. Use when the user asks to audit production readiness, run a deployment readiness check, perform a pre-release audit, validate ship-readiness, generate a production readiness report (PRR), or scan for security/observability/scalability/reliability gaps before going live. Triggers on phrases like "production readiness", "PRR", "deployment readiness", "pre-release audit", "ship-readiness", "is this prod-ready", "production audit". Supports phase flags (--only, --skip), opt-in DAST/load/visual phases (--include), caching (--cached, --fresh), and parallel execution.
    0
    installs