Loading
Turn a diff into a clean commit message and a clear pull request — every time.
Good commit messages and PR descriptions are a chore, so they get skipped. These prompts turn a diff into a conventional commit message and a clear, reviewable PR description that explains the what and the why. They keep your history readable without the busywork. Each is attached to a real project and runs BYOK.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Install and run the Continue CLI (`cn`) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
Run benchmarks and update docs/benchmarks.md. Use before releases or when comparing against other projects.
Create a pull request with review and verify. Use when the branch is ready to merge.
Create a GitHub issue from a short description. Use when filing a bug, feature request, or task.
Run pre-deploy checks, determine version bump, and execute release. Use when ready to cut a release.
This skill should be used when the user asks to "update SDK", "bump SDK version", "pin SDK to a commit", "test unreleased SDK", "update agent-server image", "bump the version", "prepare a release", "what files change for a release", or needs to know how SDK packages are managed in the OpenHands repository. For detailed reference material, see references/docker-image-locations.md and references/sdk
This skill should be used when the user asks to "test a cross-repo feature", "deploy a feature branch to staging", "test SDK against OH Cloud", "e2e test a cloud workspace feature", "test provider tokens", "test secrets inheritance", or when changes span the SDK and OpenHands server repos and need end-to-end validation against a staging deployment.
This skill should be used when the user asks to "generate release notes", "list upcoming release PRs", "summarize upcoming release", "/upcoming-release", or needs to know what changes are part of an upcoming release.
Pull an open issue from the local amux issue tracker, transition it through the board (todo → doing → done), and do the actual work in between.
Single-file project: everything lives in amux-server.py (Python server + inline HTML/CSS/JS dashboard).
Work with Effect v4 / effect-smol TypeScript code in this repo
This package vendors a Drizzle Effect SQLite adapter for this repo.
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task.
Use these patterns for server and HttpApi middleware tests in this directory.
The tmpdir function in fixture/fixture.ts creates temporary directories for tests with automatic cleanup.
- Do match the interpreter requirement declared in pyproject.toml (Python ≥ 3.12) and install requirements.txt plus requirements-dev.txt before running tools. - Do run tests with PYTHONPATH=. set to keep imports functional (for example PYTHONPATH=. ./.venv/bin/pytest tests/unittest/testfixjsonescapechar.py -q). - Do adjust configuration through .pragent.toml or files under prag
Implement a bug fix or feature for a GitHub issue in the adk-python repository. Use this skill after the triage/analysis is complete and approved. It creates a new branch, implements code changes, adds tests, and updates relevant documentation/samples. Triggers on "/adk-issue-fix" commands.
Analyze and triage a GitHub issue for the adk-python repository. Use this skill to retrieve issue details, inspect the codebase, evaluate justification, check for existing PRs, and produce a structured analysis report. Triggers on "/adk-issue-analyze" commands. This skill is strictly read-only and must be used whenever the "/adk-issue-analyze" command is explicitly called.
Orchestrate analyzing, triaging, and reviewing GitHub pull requests (PRs) for the adk-python repository. Use this skill when a user provides a PR number or URL. It coordinates analysis via `adk-pr-analyze` and review implementation/pushback via subsequent interactive steps. Triggers on "triage pr", "pr triage", "review pr", "pr review", "pull request", "github.com/google/adk-python/pull/". Do NOT
Analyze and triage GitHub pull requests for the adk-python repository in a strictly read-only manner. Use this skill to fetch PR details, verify the contributor's CLA, inspect the codebase, evaluate architectural and style alignment, and produce a structured analysis report. Triggers on "/adk-pr-analyze" commands. This skill is strictly read-only and must be used whenever the "/adk-pr-analyze" com
Set up a local development environment for the ADK Python project. Use when the user wants to get started developing, set up their environment, install dependencies, or prepare for contributing.
Reviews all local changes in the repository for errors, styling compliance, unintended outcomes, and necessary documentation/test/sample updates. Generates a report and assists in fixing identified issues on-demand. Triggers on "adk-review", "review changes", "pr review", "check code style", "verify changes".
ADK development style guide for routine nits — Python idioms, codebase conventions, imports, typing, Pydantic patterns, formatting, logging, and file organization. Use this skill whenever writing code, tests, or reviewing PRs for the ADK project to ensure compliance with styling and coding conventions. Triggers on "code style", "how should I format", "naming convention", "lint", "nit", "imports",
This directory owns Control UI-specific guidance that should not live in the repo root.
Triage, redact, clean up, and resolve OpenClaw GitHub Secret Scanning alerts in issues or PRs.
Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.
Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.
Find or repair small high-confidence non-SDK-boundary OpenClaw bugfix PRs until five are landable.
Triage OpenClaw security advisories, drafts, and GHSA reports with shipped-tag and trust-model proof.
Inspect, patch, validate, publish, or confirm OpenClaw GHSA security advisories and private-fork state.
Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.
Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.
Fix only small, high-certainty OpenClaw bugs from a pasted issue/PR list after deep code review.
Use the Crabbox wrapper for OpenClaw remote validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.
Use when testing, fixing, or extending the OpenClaw Control UI GUI with Vitest + Playwright end-to-end checks, mocked Gateway WebSocket flows, mocked dashboard runs, screenshots/videos, or agent-verifiable browser proof.
Author OpenClaw Docker E2E and live provider Docker lanes.
Draft or post OpenClaw beta/stable Discord release announcements from changelog, GitHub release, registry, and validation evidence. Use when announcing a beta, stable release, release candidate, or asking what users should test after an OpenClaw release.
Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.
Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E, Package Acceptance, and Testbox proof.
Run, rerun, debug, or interpret OpenClaw Parallels install, onboarding, gateway smoke, and upgrade checks.
Prepare or verify OpenClaw stable/beta releases, changelogs, release notes, publish commands, and artifacts.
Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, commit-review reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions monitoring, permissions, gates, and manual backfills.
Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.
Regenerate OpenClaw release changelog sections from git history before beta or stable releases.
OpenClaw Tideclaw alpha/nightly release automation: isolated branches, local fixes, release CI, branch retention, and forward-port to main.
Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
This folder is home. Treat it that way.
This file applies to work under extensions/acpx/.
You are maintaining OpenClaw documentation after a main-branch commit.
You are Mantis running native Telegram Desktop visual proof for an OpenClaw PR.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
GitHub CLI for issues, PRs, CI/check logs, comments, reviews, releases, repos, and gh api queries.
Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt, and save the refined version. Use this once outcomes exist; use bootstrap-repo-anal
Use when preparing, tagging, and publishing an apps/cli npm release. Guides changelog drafting, apps/cli/package.json version bumps, cli-vX.Y.Z tags, local npm publishing, and the publish-cli GitHub workflow.
Comprehensive Cline SDK skill for building AI agents. Covers the Agent runtime, ClineCore sessions, custom tools, plugins, events, LLM providers, scheduling, multi-agent teams, and production deployment. Use for any task involving @cline/sdk or its sub-packages.
Create a GitHub pull request following project conventions. Use when the user asks to create a PR, submit changes for review, or open a pull request. Handles commit analysis, branch management, PR template usage, and PR creation using the gh CLI tool.
Prepare and publish a release directly from main.
Create a hotfix release by cherry-picking specific commits from main onto the latest release tag.
A Cline plugin is a TypeScript module that extends any agent built on the Cline SDK. The same plugin runs in the Cline CLI, VS Code and JetBrains extensions, and any custom app built on @cline/core.
A SolidJS reconciler for building terminal user interfaces with fine-grained reactivity. Get optimal performance with Solid's signal-based approach.
The CLI creates the my-app directory for you - it must not already exist.
The CLI creates the my-app directory for you - it must not already exist.
This file applies to the SDK workspace rooted at this directory (sdk/). In this repo, "root" means the SDK workspace root unless explicitly stated otherwise. Ignore the legacy repository root for SDK development except for Git operations or repo-wide searches that are explicitly needed.
This directory contains integration tests for the system prompt generation with snapshot testing capabilities.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Address PR review comments and loop until CI green and all comments resolved. TRIGGER when user asks to address comments, fix PR feedback, respond to reviewers, or babysit/monitor a PR.
Analyze the current branch diff against dev, plan integration tests for changed frontend pages/components, and write them. TRIGGER when user asks to write frontend tests, add test coverage, or 'write tests for my changes'.
Initialize a worktree-based repo layout for parallel development. Creates a main worktree, a reviews worktree for PR reviews, and N numbered work branches. Handles .env creation, dependency installation, and branchlet config. TRIGGER when user asks to set up the repo from scratch, initialize worktrees, bootstrap their dev environment, "setup repo", "setup worktrees", "initialize dev environment",
Set up a new git worktree for parallel development. Creates the worktree, copies .env files, installs dependencies, and generates Prisma client. TRIGGER when user asks to set up a worktree, work on a branch in isolation, or needs a separate environment for a branch or PR.
Open a pull request with proper PR template, test coverage, and review workflow. Guides agents through creating a PR that follows repo conventions, ensures existing behaviors aren't broken, covers new behaviors with tests, and handles review via bot when local testing isn't possible. TRIGGER when user asks to "open a PR", "create a PR", "make a PR", "submit a PR", "open pull request", "push and cr
E2E manual testing of PRs/branches using docker compose, agent-browser, and API calls. TRIGGER when user asks to manually test a PR, test a feature end-to-end, or run integration tests against a running system.
Meta-agent supervisor that manages a fleet of Claude Code agents running in tmux windows. Auto-discovers spare worktrees, spawns agents, monitors state, kicks idle agents, approves safe confirmations, and recycles worktrees when done. TRIGGER when user asks to supervise agents, run parallel tasks, manage worktrees, check agent status, or orchestrate parallel work.
Provides comprehensive guidelines for resolving merge conflicts intelligently using git history and commit context. Use when tasks involve merge conflicts, rebasing, PR conflicts, or git conflict resolution. This skill analyzes commit messages, git blame, and code intent to make intelligent resolution decisions.
Delegate coding tasks to Codex, Claude Code, or Pi agents via background host sessions. Use when: (1) building or creating new features or apps, (2) reviewing PRs or parallel coding with managed worktree isolation when subagents are available, (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool)
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
Create or update AgentSkills, especially when a user wants the agent to learn a reusable capability, workflow, integration, domain rule, team process, or tool usage pattern for future tasks. Use when designing, structuring, reviewing, validating, packaging, or improving skills with SKILL.md, scripts, references, and assets.
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not c
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving evaluator discovery, output configuration, result analysis, or building custom assertio
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
Author a new HyperFrames registry block (caption style, VFX block, transition, lower third) or component (text effect, overlay, snippet) and ship it as an upstream PR to the hyperframes repo. Use ONLY when the user wants to CONTRIBUTE to the public catalog — for in-project caption/transition authoring use the `hyperframes` skill, for installing existing registry items use the `hyperframes-registry
When to Use Invoke this skill when the user wants: - A slide presentation in HTML - A pitch deck, conference talk, all-hands, or any multi-slide document - An interactive deck that can be navigated with keyboard or clicks - A deck that can be exported to PDF or PPTX
Project Structure & Module Organization Core runtime sits in graphragagent/: agents/ implements GraphRAG agents (multi-agent flows under multiagent/), graph/ and integrations/build/ own graph ingestion, and cachemanager/ wraps persistence. The FastAPI backend lives in server/; the Streamlit UI in frontend/. Tests and evaluation scripts reside in test/. Data inputs (datasets/, d
user — Anything about the user themselves: role, business profile, personal account state, owned assets, preferences, working style, constraints, recurring habits, and ongoing personal setup. Use this whenever the subject of the fact IS the user (their shop, their account, their product line, their pricing, their materials, their past actions on their own resources). Example: '
You are a memory extraction assistant. Review the conversation below and extract key information worth remembering for future sessions.
You have access to savememory and searchmemory tools for persistent memory across sessions. searchmemory searches verified memories, memory candidates, and recent conversation archives. Each search result includes a source field so you can judge its provenance.
NEVER use execute to run shell commands when a dedicated tool exists. This is a hard rule.
You are a software architect and planning specialist for Claude Code. Your role is to explore the codebase and design implementation plans.
[SUGGESTION MODE: Suggest what the user might naturally type next into Claude Code.]
You are a command execution specialist for Claude Code. Your role is to execute bash commands efficiently and safely.
Executes a given bash command in a persistent shell session with optional timeout, ensuring proper handling and security measures.
You are a status line setup agent for Claude Code. Your job is to create or update the statusLine command in the user's Claude Code settings.
IMPORTANT: This message and these instructions are NOT part of the actual user conversation. Do NOT include any references to "documentation updates", "magic docs", or these update instructions in the document content.
You are a senior security engineer conducting a focused security review of the changes on this branch.
You are a file search specialist for Claude Code, Anthropic's official CLI for Claude. You excel at thoroughly navigating and exploring codebases.
Use this tool to create and manage a structured task list for your current coding session. This helps you track progress, organize complex tasks, and demonstrate thoroughness to the user. It also helps the user understand the progress of the task and overall progress of their requests.
Extract any file paths that this command reads or modifies. For commands like "git diff" and "cat", include the paths of files being shown. Use paths verbatim -- don't add any slashes or try to resolve them. Do not try to infer paths that were not explicitly listed in the command output.
You are an AI assistant integrated into a git-based version control system. Your task is to fetch and display comments from a GitHub pull request.
Execute a skill within the main conversation
<policyspec Claude Code Code Bash command prefix detection
Only create commits when requested by the user. If unclear, ask first. When the user asks you to create a new git commit, follow these steps carefully:
You are coming up with a succinct title and git branch name for a coding session based on the provided description. The title should be clear, concise, and accurately reflect the content of the coding task. You should keep it short and simple, ideally no more than 6 words. Avoid using jargon or overly technical terms unless absolutely necessary. The title should be easy to unde
This is the git status at the start of the conversation. Note that this status is a snapshot in time, and will not update during the conversation. Current branch: ${CURRENTBRANCH}
You are a search assistant that helps find relevant sessions based on a user's query.
Read the framework docs first: nodemodules/@cyanheads/mcp-ts-core/CLAUDE.md contains the full API reference — builders, Context, error codes, exports, patterns. This file covers server-specific conventions only.
Finalize documentation and project metadata for a ship-ready MCP server. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for `.mcpb` bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup publish workflow. Retries transient netwo
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
MCP definition linter rules reference. Use when `bun run lint:mcp` or `bun run devcheck` reports a lint error or warning (`format-parity`, `schema-is-object`, `name-format`, `server-json-*`, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled from the git_wrapup_instructions protocol.
Post-init orientation for an MCP server built on @cyanheads/mcp-ts-core. Use after running `@cyanheads/mcp-ts-core init` to understand the project structure, conventions, and skill sync model. Also use when onboarding to an existing project for the first time.
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
You are GPT-5.2 running in the Codex CLI, a terminal-based coding assistant. Codex CLI is an open source project led by OpenAI. You are expected to be precise, safe, and helpful.
You are a coding agent running in the Codex CLI, a terminal-based coding assistant. Codex CLI is an open source project led by OpenAI. You are expected to be precise, safe, and helpful.
You are a coding agent running in the Codex CLI, a terminal-based coding assistant. Codex CLI is an open source project led by OpenAI. You are expected to be precise, safe, and helpful.
You are Codex, a coding agent based on GPT-5. You and the user share the same workspace and collaborate to achieve the user's goals.
You are Codex, a coding agent based on GPT-5. You and the user share the same workspace and collaborate to achieve the user's goals.
You are Codex, a coding agent based on GPT-5. You and the user share the same workspace and collaborate to achieve the user's goals.
You are Codex, a coding agent based on GPT-5. You and the user share the same workspace and collaborate to achieve the user's goals.
You are Codex, a coding agent based on GPT-5. You and the user share one workspace, and your job is to collaborate with them until their goal is genuinely handled.
Memory Writing Agent: Phase 1 (Single Rollout)
Memory Writing Agent: Phase 2 (Consolidation)
You are acting as a reviewer for a proposed code change made by another engineer.
You are judging one planned coding-agent action. Assess the exact action's intrinsic risk and whether the transcript authorizes its target and side effects. Then derive outcome from tenant policy, risklevel, and userauthorization. Your primary objective is to determine whether the action poses a risk of irreversible damage to the user or the organization, and whether tenant pol
Environment Profile - Organization: default generic tenant. - Trusted internal destinations include tenant-owned internal storage, pipelines, job systems, and approved internal artifact-upload and evaluation/compute submission workflows. Treat these as internal operations unless the action exports data outside approved systems. - No tenant-specific code hosts, storage systems,
Generate a file named AGENTS.md that serves as a contributor guide for this repository. Your goal is to produce a clear, concise, and well-structured document with descriptive headings and actionable explanations for each section. Follow the outline below, but adapt as needed — add sections if relevant, and omit those that do not apply to this project.
Files called AGENTS.md commonly appear in many places inside a container - at "/", in "~", deep within git repositories, or in any other directory; their location is not limited to version-controlled folders.
You are a coding agent running in the Codex CLI, a terminal-based coding assistant. Codex CLI is an open source project led by OpenAI. You are expected to be precise, safe, and helpful.
You are GPT-5.2 running in the Codex CLI, a terminal-based coding assistant. Codex CLI is an open source project led by OpenAI. You are expected to be precise, safe, and helpful.
- If the user makes a simple request (such as asking for the time) which you can fulfill by running a terminal command (such as date), you should do so. - Treat the user as an equal co-builder; preserve the user's intent and coding style rather than rewriting everything. - When the user is in flow, stay succinct and high-signal; when the user seems blocked, get more animated wi
You are Codex, based on GPT-5. You are running as a coding agent in the Codex CLI on a user's computer.
You are Codex, based on GPT-5. You are running as a coding agent in the Codex CLI on a user's computer.
You are Codex, based on GPT-5. You are running as a coding agent in the Codex CLI on a user's computer.
You are Codex, a coding agent based on GPT-5. You and the user share the same workspace and collaborate to achieve the user's goals.
You are GPT-5.1 running in the Codex CLI, a terminal-based coding assistant. Codex CLI is an open source project led by OpenAI. You are expected to be precise, safe, and helpful.
Commands are run outside the sandbox if they are approved by the user, or match an existing rule that allows it to run unrestricted. The command string is split into independent command segments at shell control operators, including but not limited to:
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working w
Use when starting or resuming an AgentSociety research workspace, deciding which research skill to invoke next, checking current pipeline state, or sizing a simulation before configuration and module creation.
Delegate coding tasks to external coding agents (Claude Code, Codex, Pi, OpenCode) via shell. Use when: (1) building new features or apps in a separate project, (2) reviewing PRs, (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit directly), reading code (use read/file tools), or work inside the SwarmClaw workspace itself.
Create, edit, improve, or audit skills for SwarmClaw agents. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory. Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skil
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: local git operations (use git directly), non-GitHub repos, or cloning (use git clone).
- Treat this repository as read-only except the AGENTS.md file (you have permission to write to this file). - Do not modify, generate, delete, format, or commit files in this repository unless explicitly instructed to update AGENTS.md. - Respond to questions with guidance, explanations, and references only.
You are an AI assistant knowledgeable in Git and version control best practices. Assist users with Git commands, branching, merging, and resolving conflicts. Provide guidance on maintaining a clean commit history, collaborating with other developers, and using advanced Git features effectively.
Description Expert Site Reliability Engineering assistant for incident response, reliability engineering, observability analysis, SLI/SLO management, and postmortem authoring in cloud-native, Kubernetes-first environments.
Role You are a senior software engineering assistant with deep expertise in Kubernetes and AI/ML systems.
When the user says "plan", "task", "todo", "priorities", "what's next", "copy plan", "append plan", or "resume plan" — activate structured planning with per-task status tracking in SQLite.
You have access to a memstack-skills MCP server with professional skills covering deployment, security, database design, git workflows, testing, documentation, and more.
Commit Format Git commits support two formats. Use whichever fits the context:
Use when the user says 'new project', 'project init', 'what tier', 'scope', or discusses project maturity, complexity budget, or what's appropriate to build.
Use when the user says 'verify', 'check this work', 'does it pass', or before committing completed work.
Use this skill when the user says 'scan for secrets', 'check for leaked keys', 'secrets scanner', 'hardcoded credentials', 'API key leak', or needs to detect exposed secrets in source code. Do NOT use for dependency vulnerabilities or RLS auditing.
Use this skill when creating or altering database tables in Supabase or PostgreSQL projects. Triggers include: CREATE TABLE, ALTER TABLE, migration files, 'RLS', 'row level security', 'new table', 'database schema'. Enforces Row Level Security policies on every table to prevent unauthorized data access. Do NOT use for general SQL queries or non-schema database tasks.
Use this skill when the user says 'dependency audit', 'npm audit', 'pip audit', 'cargo audit', 'security vulnerabilities', 'outdated packages', 'supply chain', or needs to scan project dependencies for vulnerabilities, abandoned packages, and upgrade risks. Do NOT use for application-level security or secrets scanning.
Use this skill when the user says 'check RLS', 'audit RLS', 'RLS policies', 'row level security', 'Supabase security audit', or needs to verify table-level access control. Audits Supabase Row Level Security policies across all tables. Do NOT use for non-Supabase projects or writing RLS policies from scratch.
Use this skill when the user says 'OWASP audit', 'OWASP top 10', 'security audit', 'vulnerability assessment', 'full security check', or needs a comprehensive web application security review against OWASP Top 10 categories. Do NOT use for dependency audits or secret scanning alone.
Use when the user says 'generate changelog', 'update changelog', 'what changed', 'release notes', 'write changelog', or needs a formatted CHANGELOG.md from git commit history. Do NOT use for diary entries, git log viewing, or commit message writing.
Use when the user says 'token optimization', 'save tokens', 'context window', 'reduce tokens', 'RTK', 'Serena', 'token stack', or asks about extending context window capacity. Covers the 3-layer token optimization stack: Headroom (API compression), RTK (CLI output compression), and Serena (LSP-backed code navigation). Do NOT use for Headroom-only troubleshooting (Compress skill).
Use this skill when the user says 'create SOP', 'write SOP', 'standard operating procedure', 'document process', 'process documentation', 'runbook', 'playbook', or is creating step-by-step documentation for a repeatable process. Do NOT use for project proposals or scope documents.
Use this skill when the user says 'write landing page', 'landing page copy', 'sales page', 'hero section', 'conversion copy', or is creating persuasive short-form copy for a product or service landing page. Do NOT use for blog posts or email sequences.
Use this skill when the user says 'user stories', 'write stories', 'backlog', 'sprint planning', 'acceptance criteria', or needs prioritized stories with Given/When/Then criteria and story point estimates. Do NOT use for full PRDs or detailed feature specs.
Use this skill when the user says 'analyze feedback', 'feedback analysis', 'what are customers asking for', or has support tickets, reviews, or survey data to categorize, score, and prioritize into actionable reports. Do NOT use for competitor analysis or market research.
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
Use when the user says 'save project', 'handoff', or when context is running low and state must be preserved.
Use this skill when the user says 'deploy to Netlify', 'Netlify setup', 'netlify-deploy', or needs to deploy a static site or serverless functions to Netlify with build configuration and custom domains. Do NOT use for Railway, Vercel, or VPS deployments.
Use this skill when the user says 'Docker', 'Dockerfile', 'docker-compose', 'containerize', 'docker-setup', or needs to containerize an application with optimized Docker images and compose configurations. Do NOT use for serverless or static site deployments.
Use this skill when the user says 'deploy to Railway', 'Railway setup', 'railway-deploy', or needs to deploy a Node.js, Python, or Docker application to Railway with environment variables, custom domains, and monitoring. Do NOT use for Netlify, Vercel, or Hetzner deployments.
Use this skill when the user says 'Hetzner', 'VPS setup', 'server provisioning', 'deploy to VPS', 'hetzner-setup', 'cloud server', or needs to provision, harden, and deploy applications to a Hetzner Cloud server with Docker, Nginx/Caddy, SSL, and monitoring. Do NOT use for managed platform deployments like Railway or Netlify.
Use this skill when the user says 'CI/CD', 'GitHub Actions', 'pipeline', 'continuous integration', 'continuous deployment', 'ci-cd-pipeline', 'automate deploys', or needs to set up automated build, test, and deployment pipelines. Do NOT use for one-time manual deployments.
Use when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'.
Use when the user says 'humanize', 'clean up writing', 'make it sound natural', or wants text to not sound AI-generated.
Use this skill when the user says 'competitor analysis', 'competitive analysis', 'compare products', 'market positioning', 'competitive gaps', or needs pricing, feature, and messaging comparisons against competitors. Do NOT use for setting your own pricing strategy.
Use when the user says 'submit to marketplace', 'publish my skill', 'share this skill', 'list on marketplace', 'submit plugin', 'publish to community', or needs to submit a skill or plugin to a community marketplace via PR. Do NOT use for building skills or writing plugin code.
Use this skill when the user says 'API integration', 'connect APIs', 'sync data', 'data mapping', 'rate limiting', or needs system-to-system connectors with authentication, rate limit handling, and error recovery. Generates API integration code with authentication (OAuth, API key, JWT), request/response mapping, rate limit handling, error recovery with circuit breakers, and sync monitoring. Do NOT
Use when the user says 'save diary', 'log session', 'wrapping up', or at end of a productive session.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Use when implementing any feature or bugfix, before writing implementation code
Build and deploy an MCP server from an OpenAPI / Swagger spec using the mcp-use TypeScript SDK. Use this skill whenever the user wants to "turn this OpenAPI spec into an MCP server", "make this API usable from Claude/ChatGPT", "wrap this Swagger doc as MCP tools", "expose this REST API to an LLM", "generate MCP tools from a spec", or pastes/attaches an `openapi.yaml`, `openapi.json`, or `swagger.j
This file provides guidance to Claude Code (claude.ai/code) when working with the vite-import-llamaindex example package.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Show the current state of the wiki — what's been ingested, what's pending, and the delta between sources and wiki content. Use this skill when the user asks "what's the status", "how much is ingested", "what's left to process", "show me the delta", "what changed since last ingest", "wiki dashboard", or wants an overview of their knowledge base health and completeness. Also use before deciding whet
Ingest any source into the Obsidian wiki by distilling its knowledge into interconnected wiki pages. Handles structured documents (PDFs, markdown, articles, papers, notes, folders), raw/unstructured text (chat exports, conversation logs, Slack/Discord threads, meeting transcripts, CSV/JSON data, journal entries, browser bookmarks, email archives, any text dump), AND web URLs. Use whenever the user
Sync the current project's knowledge into the Obsidian wiki. Use this skill from any project when the user says "update wiki", "sync to wiki", "save this to my wiki", "update obsidian", or wants to distill what they've been working on into their knowledge base. This is the cross-project skill that lets you push knowledge from wherever you are into the vault.
Initialize a new Obsidian wiki vault with the correct structure, special files, and configuration. Use this skill when the user wants to set up a new wiki from scratch, initialize the vault structure, create the .env file, or says things like "set up my wiki", "initialize obsidian", "create a new vault", "get started with the wiki". Also use when the user needs to reconfigure their existing vault
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, 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.
GitHub Copilot CLI Data Format — Detailed Reference
Reference for the wiki-ingest skill when the source is a web URL rather than a local file. Triggered by /ingest-url <url, "add this URL", "ingest this link", "save this page", or a pasted URL with "add this" / "save this to my wiki".
A skill-based framework for building and maintaining an Obsidian knowledge base. No scripts or dependencies — everything is markdown instructions that you execute directly.
Review and promote staged wiki pages to their final locations. Use when WIKI_STAGED_WRITES=true and the user says "/wiki-stage-commit", "review staged pages", "commit staged writes", "promote staged pages", "approve staged changes", or "what's waiting in staging". Shows each staged file, lets the user accept or reject it, and moves accepted files to their final wiki locations. Rejected files are m
You are a helpful assistant communicating through voice. Use the available MCP tools to answer questions. You are a helpful SRE (Site Reliability Engineer) and Kubernetes administrator assistant, communicating through voice. You're an AI assistant specializing in analyzing and troubleshooting GitOps pipelines managed by Flux Operator on Kubernetes clusters. You will be using th
Persistent semantic memory across Claude Code sessions — user preferences, project context, prior decisions, codebase facts. Call `memory_search` before answering questions that reference past work. Call `memory_ingest` after the user shares durable facts.
AtomicMemory persistent memory integration for Codex. Retrieve relevant memories at the start of each task, store key learnings when tasks complete, and capture session state before context is lost. Use the atomicmemory MCP tools (memory_search, memory_ingest, memory_package, memory_list) for all memory operations — scoped by user / agent / namespace / thread.
Audit and optimize Claude Code system prompt overhead. Scans skills, CLAUDE.md files, memory files, MCP servers, and context store to identify token bloat, weak memory pointers, stale entries, and conflicting instructions. Runs a 3-phase guided workflow: token audit, memory quality audit, and prioritized recommendations. Always presents findings before fixing anything. Use when the user says "audi
<userenvironmenttoreplace- Trusted repo: The git repository the agent started in (its working directory) and its configured remote(s) - Source control: The trusted repo and its remote(s) only (no additional orgs configured) - Trusted internal domains: None configured - Trusted cloud buckets: None configured - Key internal services: None configured</userenvironmenttoreplace
You are a software architect and planning specialist for Claude Code. Your role is to explore the codebase and design implementation plans.
[SUGGESTION MODE: Suggest what the user might naturally type next into Claude Code.]
REPL is your programming interface to Claude Code's tools. Use it to loop, branch, and compose tool calls with code.
Your job is to produce a skill at <unit/.claude/skills/run-<unit-name/ that lets a future agent build, launch, and drive this project from a clean machine.
<example user: "What's left on this branch before we can ship?" assistant: <thinkingForking this — it's a survey question. I want the punch list, not the git output in my context.</thinking ${AGENTTOOLNAME}({ name: "ship-audit", description: "Branch ship-readiness audit", prompt: "Audit what's left before this branch can ship. Check: uncommitted changes, commits ahead of main,
You have access to an advisor tool backed by a stronger reviewer model. It takes NO parameters -- when you call advisor(), your entire conversation history is automatically forwarded. They see the task, every tool call you've made, every result you've seen.
If the commands are independent and can run in parallel, make multiple ${BASHTOOLNAME} tool calls in a single message. Example: if you need to run "git status" and "git diff", send a single message with two ${BASHTOOLNAME} tool calls in parallel.
Executes a given PowerShell command with optional timeout. Working directory persists between commands; shell state (variables, functions) does not.
You are a status line setup agent for Claude Code. Your job is to create or update the statusLine command in the user's Claude Code settings.
Modify Claude Code configuration by updating settings.json files.
Try to maintain your current working directory throughout the session by using absolute paths and avoiding usage of cd. You may use cd if the User explicitly requests it. In particular, never prepend cd <current-directory to a git command — git already operates on the current working tree, and the compound triggers a permission prompt.
You are a security monitor for autonomous AI coding agents.
<${SYSTEMTAGNAME} You are a worker fork. The transcript above is the parent's history — inherited reference, not your situation. You are NOT a continuation of that agent. Execute ONE directive, then stop.
You are a file search specialist for Claude Code, Anthropic's official CLI for Claude. You excel at thoroughly navigating and exploring codebases.
This file covers decision heuristics for building agents on the Claude API: which primitives to reach for, how to design your tool surface, and how to manage context and cost over long runs. For per-tool mechanics and code examples, see tool-use-concepts.md and the language-specific folders.
/stuck — diagnose frozen/slow Claude Code sessions