aif-skills

Plugin aif-skills from marketplace aifgrouplaos in aifgrouplaos/ai-skills. Commands read from the repo's manifest — 12 days ago.

Skills (41)

• wiki-publish

  Publish markdown to the Company wiki through Wiki.js GraphQL — bootstrap an ephemeral working copy, then create or update live pages. User-invoked only.

• wiki-write-lao

  Translate one English Wiki page (/en/…) into Lao — read English, write a Lao working copy under the Company wiki's Thai Wiki.js locale. Never publishes. User-invoked only.

• wiki-write

  Author one English Company wiki page from a live standards template — project name, pick a template, grill placeholders, write a working copy. Never publishes. User-invoked only.

• ask-matt

  Ask which skill or flow fits your situation. A router over the skills in this repo.

• cherry-pick-to-main

  Prepare a feature branch created from `develop` for a selected target branch such as `main` or `uat`, creating a target-prefixed branch and cherry-picking only that feature's commits. Use when a feature needs a separate branch based on a chosen target.

• code-review

  Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them s

• codebase-design

  Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

• debug-mantra

  Four-mantra debugging discipline — reproduce, trace the fail path, falsify the hypothesis, cross-reference every breadcrumb. Recite the mantra block verbatim at the start of any debugging session, then apply the four steps in order before proposing any fix. Trigger on /debug-mantra and proactively w

• diagnosing-bugs

  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

• domain-modeling

  Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.

• evidence-research

  Evidence-first research using search/browsing tools, primary sources, and source-backed synthesis, with upfront user-intent grilling when the research goal is ambiguous. Use when the user asks to investigate a prompt or question, find accurate/current information, compare claims, gather references,

• explain-codebase

  Analyzes a repository end-to-end and explains architecture, modules, data flow, and key code paths in accurate technical terms using plain, easy-to-understand language, walking key code line by line with examples. Use when the user asks to understand the project, explain the codebase, onboard to a r

• grill-with-docs

  A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

• implement

  Implement a piece of work based on a spec or set of tickets.

• improve-codebase-architecture

  Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

• nestjs

  Guides NestJS code changes with a structure-first workflow. Use when implementing, refactoring, debugging, or reviewing code in an existing or new NestJS project, including standard and monorepo workspaces and REST, GraphQL, WebSocket, or microservice components.

• post-mortem

  Write the canonical engineering record of a fixed bug — root cause, mechanism, fix, validation, and how it slipped through. Engineer-audience, code identifiers welcome. Use after a debug session lands a fix, before closing the ticket. Trigger on /post-mortem, when the user says "write the post-morte

• prototype

  Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

• qwen-agent

  Delegate menial, well-scoped coding tasks to a cheap Qwen-backed subagent via the `claude-9arm` command instead of burning Claude tokens/quota. Use when the work is mechanical and low-risk — bulk renames, formatting, boilerplate, find-replace, grep-style search & summarization, reading/condensing lo

• refactor

  Use when refactoring existing code to improve readability or maintainability while preserving behavior.

• research

  Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

• resolving-merge-conflicts

  Use when you need to resolve an in-progress git merge/rebase conflict.

• scrutinize

  Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler/more elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and ever

• setup-matt-pocock-skills

  Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

• tdd

  Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

• to-spec

  Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

• to-tickets

  Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

• triage

  Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

• wayfinder

  Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

• wizard

  Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can pe

• caveman

  Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman"

• docx-code-formatter

  Format terminal commands, script blocks, and inline technical identifiers in DOCX documents. Use when formatting code or commands inside Word documents.

• grill-me

  A relentless interview to sharpen a plan or design.

• grilling

  Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

• handoff

  Compact the current conversation into a handoff document for another agent to pick up.

• management-talk

  Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA comment, Slack post, async standup line, email, or meeting talking-points. Trigger when the user asks

• qwenchance

  Keeps a long Claude Code task on-track — breaks out of looping/circular thinking, watches the context budget, bounds internal reasoning, and triggers a clean handoff before the window fills. Use when the model is repeating steps, re-reading the same files, second-guessing in circles, stuck or spinni

• teach

  Teach the user a new skill or concept, within this workspace.

• to-questionnaire

  Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

• wait-what

  Stop. That last message did not land: re-pitch it.

• writing-for-agents

  Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Similar plugins