avav25
- 127 skills
- 0 followers
- last month last updated
- ▌ Create Pr · avav25Use this skill when ready to submit code for review, opening a draft PR, or pushing a branch for review — to create a pull request by collecting the diff, generating a PR description with context, applying a checklist, and pushing, detecting .github/PULL_REQUEST_TEMPLATE.md + CODEOWNERS + stacked-PR tools (Graphite / Sapling / git-spice).
- ▌ Docs Pack · avav25 bundleUse this skill when onboarding users to a feature, producing API documentation, or writing operational procedures — to generate a user-facing documentation pack (README, API reference, runbook, tutorial) for a module or feature; distinct from the `docs` knowledge skill — `docs-pack` produces git-versioned user docs while `docs` is general documentation guidance.
- ▌ Humanizer · avav25 bundleUse this skill when editing, reviewing, or producing any public-facing text — blog posts, social media, UI copy, emails, landing pages, documentation — to remove signs of AI-generated writing by detecting and fixing AI patterns including inflated symbolism, promotional language, vague attributions, em dash overuse, rule of three, AI vocabulary, negative parallelisms, sycophantic tone, and filler phrases.
- ▌ Marketing · avav25 bundleUse this skill when running any daily/weekly/monthly marketing task in a project that already has marketing/MARKETING.md — the recurring marketing operations dispatcher for social posts, blog posts, email campaigns, trend research, analytics, content repurposing, community engagement, and strategy review. For first-time strategy setup, use /marketing-init.
- ▌ Run Tests · avav25Use this skill when verifying code by running tests, analyzing failures, or addressing coverage gaps — to run the test suite, analyze failures, auto-fix obvious issues, and re-run; serves as a sub-workflow for /develop, /bugfix, and /pre-commit and uses the `test-strategy` skill.
- ▌ AI Skills · avav25 bundleCreate, modify, validate, and analyze Codex-native AI assets such as AGENTS.md files, shared skills, roles, rules, operations, templates, and checklists.
- ▌ Blog Post · avav25Blog post workflow — research topic, create content brief, write article, SEO optimize, quality review with feedback loop. Orchestrates product-manager, content-writer, and seo-engineer roles for public blog content creation and updates.
- ▌ Geo Writer · avav25 bundleUse this skill when writing or editing public-facing text intended to be cited or quoted by LLMs (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews) — blog posts, landing pages, help articles, FAQ blocks, programmatic SEO templates, pillar guides — to optimize that text for GEO/AEO (Generative Engine Optimization and Answer Engine Optimization).
- ▌ Pre Commit · avav25Use this skill when running a quality gate over staged changes before a git commit to catch lint/format/type/test failures — a pre-commit quality gate that lints, formats, type-checks, tests, and validates before committing. Detects existing pre-commit framework / Husky / Lefthook / lint-staged and routes to it; otherwise runs an inline stack-detected gate. Not the [pre-commit framework](https://pre-commit.com) itself — see Step 0 for framework detection.
- ▌ SEO Review · avav25Use this skill when auditing a public-facing page or site for search visibility, before publishing a marketing or blog page, when traffic drops or indexing issues are suspected, when validating JSON-LD / Open Graph / canonical / sitemap setup, or as the SEO gate inside `/content-creation` and `/docs-pack` — to run the SEO review workflow (technical SEO audit, meta tags, structured data validation, Core Web Vitals, crawlability, indexability, AI search readiness) applying the SEO Engineer role.
- ▌ Test Local · avav25Use this skill when running a full local QA cycle before commit or PR — a local dev testing workflow that verifies the test environment, provisions infrastructure (Docker, Testcontainers), runs a multi-level test suite (unit → integration → E2E), performs coverage analysis, and applies a quality gate. Applies the QA Engineer role.
- ▌ Code Review · avav25 bundleUse this skill when reviewing a pull request, merge request, or code change before merge, conducting an architecture review, auditing code for security/performance/quality, or running a pre-merge quality gate — including when applied by a Reviewer or QA subagent — to produce a verdict (APPROVE / REQUEST_CHANGES / COMMENT) using Google's eng-practices framing (code health over perfection) and conventional comments vocabulary (nit / suggestion / issue / praise). Distinct from /security-scan (no dependency CVE scan) and /security-audit (no full OWASP audit).
- ▌ Env Analyze · avav25Use this skill when troubleshooting a deployment, debugging CI flakes, validating an environment before deployment, or when local diagnostics need to span more than just Docker — the multi-scope environment diagnostic covering Kubernetes, CI runner, network, resource usage, and a cross-scope drift snapshot for baselining across runs, with optional `--auto-fix` for container-level safe actions. For Docker-only local triage use `/analyze-local`. Not for code bugs (use /bugfix) or application-level diagnostics (use /spike).
- ▌ Feature Dev · avav25Use this skill when explicit single-agent inline execution is requested or `/develop` is impractical for the situation — to run a single-agent fallback for feature implementation that detects tech stack and applies one engineering role inline (no Developer/Reviewer/QA spawning). The canonical Anthropic `Agent` tool is always available in modern Claude Code, so `/develop` (multi-agent pipeline) should be the default and this fallback should be selected only on a documented technical block.
- ▌ QA · avav25Use this skill when the user asks to validate a feature, write or improve tests, report a bug, or audit acceptance criteria coverage — /qa = QA-task workflows (verification, test creation, bug reports, exploratory). /test-strategy = test design principles + pyramid + coverage targets (knowledge). /test-local = test execution workflow.
- ▌ Docs · avav25Use this skill when the user asks to edit internal markdown documentation and source code must stay untouched — the internal documentation workflow to edit technical docs, ADRs, PRDs, design notes, release notes, and UI microcopy without touching source code, applying the Content Writer role. For public-facing blog posts, landing pages, and marketing content use `/content-creation` (it owns the GEO/SEO/humanizer pipeline). For full multi-document user-facing packs (README + API ref + runbook + tutorial) use `/docs-pack`.
- ▌ Eval · avav25Use this skill when running pre-release validation, detecting calibration regression, or tuning a skill — to run plugin evaluation tiers (Tier 1 linters and Tier 2 judge-calibration drift smoke) by wrapping the eval/runner.py harness. Tier 1 is free (no LLM); Tier 2 budgets tokens per `eval/config.json`. Tier 3 (full behavioral suites) is planned but not yet shipped — runner returns error code 3 if invoked.
- ▌ Plan · avav25 bundleUse this skill when the user has a PRD or feature brief and needs an executable plan before code is written — to plan feature implementation across services and roles by parsing the PRD/feature brief, reading project architecture (ARCHITECTURE.md, CLAUDE.md), decomposing into work packages per service/role with complexity estimates, and running a multi-reviewer feedback loop (product-manager + solution-architect + system-architect).
- ▌ Ralph · avav25 bundleUse this skill when iterating a task until a binary success condition holds (test passes, schema validates, output matches a regex) and a power user wants a standalone RALF (Read-Act-Learn-Feedback) iteration loop — to wrap the task in a feedback loop with a mechanically-verifiable oracle and a kill-on signal. Not for open-ended exploration — use /spike for that.
- ▌ Spike · avav25 bundleUse this skill when evaluating new tech, prototyping approaches, researching unknowns, or building a proof-of-concept — for a time-boxed exploration with a go/no-go writeup, single-pass with optional reviewer and no RALF (a spike is exploration, not convergence). Not for development (use /develop) or decisions already made.
- ▌ Bugfix · avav25 bundleUse this skill when investigating, diagnosing, and fixing a reported bug — including when the user reports an error message or broken behavior without saying "bugfix" — to run an end-to-end bugfix workflow with a mandatory DEVELOP → REVIEW → QA pipeline: the Lead orchestrates triage intake, environment analysis (`/env-analyze` for local, `/analyze-prod` for production), evidence collection, and bug report, then spawns developer/reviewer/QA via the Anthropic `Agent` tool to apply, review, and verify the fix.
- ▌ Analyze · avav25 bundleUse this skill when the user asks to analyze, investigate, assess, evaluate, compare, or research a codebase, architecture, system, product, market, or research topic in a structured way — including requests that need explicit scope, framework-driven reasoning, and separated facts/inference/recommendation but do not use the word "analyze" — to run a deep analysis workflow producing traceable scope, evidence, and conclusions. Not for quick one-off lookups or implementation work — this is an investigation-and-conclusions workflow.
- ▌ Develop · avav25 bundleUse this skill when implementing a feature with the canonical Anthropic `Agent` tool available — the multi-agent feature implementation pipeline (DEVELOP → REVIEW → QA with developer(s), reviewer, QA, and lead orchestrator) that spawns specialized subagents via the Agent tool (`subagent_type: "ai-skills:<role>"`); preferred over the single-agent /feature-dev fallback.
- ▌ Migrate · avav25 bundleUse this skill when planning database schema changes with rollback, framework version upgrades, or library replacements — a planned migration with rollback plan across schema, library, version, and framework, run as a multi-agent pipeline with RALF on validation. Not for refactors without external contract change (use /refactor) or small bug-fix releases (use /develop).
- ▌ Release · avav25Use this skill when cutting a release, tagging a version, preparing a changelog, or publishing release notes — to run the release workflow (version bump, changelog generation, signed git tag, release notes) which detects existing release tooling (release-please, semantic-release, Changesets, GoReleaser, cargo-release, JReleaser) and routes to it, otherwise runs an inline stack-detected release.
- ▌ Product · avav25Feature design workflow — transform raw feature inputs (ideas, research, stakeholder requests, competitive analysis) into a structured PRD or feature brief. Applies product-manager role. Produces PRD, user stories, acceptance criteria, success metrics, and updates FEATURES.md. First step in the planning chain, precedes architecture skill and plan skill. Includes mandatory multi-reviewer feedback loop with product-manager, marketing-strategist, content-writer, and seo-engineer.
- ▌ Feedback · avav25 bundleUse this skill when reviewing how the plugin behaved across recent runs, after a release to confirm reliability, before filing a plugin bug report, or when planning the next plugin improvement cycle — to collect and analyze past Claude Code session logs for the ai-skills plugin and surface agent, subagent, skill, command, and hook errors, timeouts, unexpected exits, and other anomalies that point at plugin defects. Defaults to the last 7 days of sessions for the current project. Produces an extended Markdown report on disk plus a brief on-screen summary.