Loading
Prompts that review a diff like a senior engineer — catching real bugs, not nitpicks — and explain why each change matters.
A good code review finds the bug that ships, not the missing semicolon. These prompts review a diff or pull request the way a senior engineer would: prioritising correctness, edge cases, and security over style. They explain the reasoning behind each comment so you learn, not just patch. Each one is attached to a real project and runs on the model of your choice.
Dogfooding: this project uses its own product concept.
Dogfooding: this project uses its own product concept.
This repository is a monorepo. Each library lives in a subdirectory under libs/.
This repository is a monorepo. Each library lives in a subdirectory under libs/.
Style guidelines for writing and updating documentation. Use when writing new docs, updating existing docs, or reviewing docs for quality.
This file provides guidance to AI coding agents when working with code in this repository.
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.
Create a pull request with review and verify. Use when the branch is ready to merge.
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.
This repository contains the code for OpenHands, an automated AI software engineer. It has a Python backend (in the openhands directory) and React frontend (in the frontend directory).
/review-session-log — Review a session's terminal log
Current Goals - Primary goal: [e.g. "Gain 10 lbs by end of Q2 (145 → 155 lbs)"] - Secondary: [e.g. "Improve squat 1RM from 225 to 275"]
The tmpdir function in fixture/fixture.ts creates temporary directories for tests with automatic cleanup.
- To regenerate the JavaScript SDK, run ./packages/sdk/js/script/build.ts. - The default branch in this repo is dev. - Local main ref may not exist; use dev or origin/dev for diffs.
- 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
Use for any git operation (commit, push, pull, rebase, branch, PR, cherry-pick, etc.). Provides commit message format and conventions.
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
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 document provides context for AI coding assistants (Antigravity, Gemini CLI, etc.) to understand the ADK Python project and assist with development.
Triage, redact, clean up, and resolve OpenClaw GitHub Secret Scanning alerts in issues or PRs.
Find or repair small high-confidence non-SDK-boundary OpenClaw bugfix PRs until five are landable.
Build and review high-quality technical docs as well as agent instruction files in your repository.
Add a redacted agent transcript section to GitHub PR or issue bodies during OpenClaw agent-created PR/issue workflows.
Use immediately for any pasted OpenClaw GitHub issue or PR URL/number, and for OpenClaw issue/PR review, triage, duplicate search, opener identity/who wrote it, author account age/activity, comments, labels, close, land, or maintainer evidence checks.
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.
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 reviewing, reproducing, or proving OpenClaw Telegram behavior with a real Telegram user on Crabbox, including PR review workflows that need an agent-controlled Telegram Desktop recording, TDLib user-driver commands, Convex-leased credentials, WebVNC observation, and motion-trimmed artifacts.
Author OpenClaw Docker E2E and live provider Docker lanes.
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.
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.
Use gitcrawl to search duplicate OpenClaw PRs/issues, group related work in prtags, and sync duplicate state to GitHub.
Use for OpenClaw clawtributors PR/issue triage: Discrawl discovery, live-open rechecks, deep review, topic grouping, and compact @handle/LOC/type/blast/verification summaries.
Auto Review closeout. Codex review is the default when no engine is set and is the recommended reviewer.
OpenClaw builds a custom system prompt for every agent run. The prompt is OpenClaw-owned and does not use a runtime default prompt.
This folder is home. Treat it that way.
OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.
Use gh for GitHub issues, PR status, CI/logs, comments, reviews, releases, and API queries.
Lobster executes multi-step workflows with approval checkpoints. Use it when:
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.
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
First-time analysis of a repository with no prior reviewer outcomes. Crawl historical merged-PR review feedback with the gh CLI (plus any preloaded samples), extract the team's review norms, and synthesize the initial per-repo review-style prompt. Use this for a cold-start repo; use continual-learning instead once the reviewer has accumulated finding outcomes.
This file provides guidance to Coding Agents when working with code in this repository.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
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.
Create a hotfix release by cherry-picking specific commits from main onto the latest release tag.
The Cline SDK supports scheduled, one-off, and event-driven agent execution through the automation subsystem in @cline/core.
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 multi-turn conversational agent in the terminal with streaming output:
Components for displaying code with syntax highlighting and diffs in OpenTUI.
Variables: !<INPUT 0! -- Commonset !<INPUT 1! -- Surrounding schedule description !<INPUT 2! -- Persona first name !<INPUT 3! -- Persona first name !<INPUT 4! -- Current action !<INPUT 5! -- curr time range !<INPUT 6! -- Current action duration in min !<INPUT 7! -- Persona first names
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.
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.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
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.
Review a PR for correctness, security, code quality, and testing issues. TRIGGER when user asks to review a PR, check PR quality, or give feedback on a PR.
Alternate /pr-review and /pr-address on a PR until the PR is truly mergeable — no new review findings, zero unresolved inline threads, zero unaddressed top-level reviews or issue comments, all CI checks green, and two consecutive quiet polls after CI settles. Use when the user wants a PR polished to merge-ready without setting a fixed number of rounds.
This file provides guidance to coding agents when working with code in this repository.
This guide provides context for coding agents when updating the autogptplatform folder.
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)
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]
This is your operations center. Read this on every session start.
Translate an existing Remotion (React-based) video composition into a HyperFrames HTML composition. Use ONLY when the user explicitly asks to port, convert, migrate, translate, or rewrite a Remotion composition as HyperFrames (e.g. "port my Remotion project to HyperFrames"). Do NOT use when (a) authoring a NEW HyperFrames composition (even if A/B-testing a Remotion video); (b) Remotion is mentione
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
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
Critique the following draft produced for the task.
GPT Description: A Multi-Agent Multi-Tasking Assistant. Seamlessly switches personas with different skills and backgrounds to tackle complex tasks. Powered by Mr Persona. - By Shane Kretzmann
GPT Description: A GPT policy reviewer that assists GPT makers by checking if their GPTs adhere to OpenAI's usage policies. Compliance Guard gives an indication of what you need to fix or change. Keep your GPTs alive! Uses OpenAI policy and ChatGPT policy. Don't get a ban. GPT Police ! - By bahouprompts.com
GPT Description: 📊 Rate, Find & Fix Your Socials - By probsolvio.com
Marketing covers: - Content strategy and creation (blog, social, email, video) - Brand identity and guidelines - Campaign planning and execution - Lead generation (top of funnel) - Market positioning and messaging - Analytics and performance reporting
Dev covers: - Software architecture and technical decisions - Feature implementation and bug fixes - Code review and quality gates - Testing strategy and execution - Technical documentation - Developer tooling and workflows
You are an expert code reviewer. Follow these steps:
Analyze the following conversation between a user and an assistant (assistant responses are hidden).
You are a senior security engineer conducting a focused security review of the changes on this branch.
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.
on: issuecomment: types: [created] pullrequestreviewcomment: types: [created] issues: types: [opened, assigned] pullrequestreview: types: [submitted]
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
\uD83E\uDD16 Installing Claude Code GitHub App
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:
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.
Scaffold a new MCP prompt template. Use when the user asks to add a prompt, create a reusable message template, or define a prompt for LLM interactions.
File a bug or feature request against @cyanheads/mcp-ts-core when you hit a framework issue. Use when a builder, utility, context method, or config behaves contrary to the documented API — not for server-specific application bugs.
Post-session code review and cleanup against a working tree of changes. Analyzes `git diff` to simplify, consolidate, and align changed code with the existing codebase — modernize syntax, remove unnecessary complexity, consolidate duplicated logic, catch efficiency issues. Use after a substantive working session, or when asked to clean up, simplify, reduce slop, consolidate, modernize, tighten up,
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)
You are acting as a reviewer for a proposed code change made by another engineer.
Continue working toward the active thread goal.
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.
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.
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:
Haystack uses Hatch for environment and dependency management.
Azure AI Travel Agents - Developer Guide
Skybridge is a fullstack TypeScript framework for building ChatGPT Apps and MCP Apps — interactive React views that render inside AI conversations.
Enforce academic writing and LaTeX drafting conventions for EasyPaper outputs.
Use when creating or revising a custom agent type, when an experiment needs an agent class that does not yet exist in the workspace, or when the agent design must be sized against a simulation budget.
Use when creating or revising a custom environment module, when an experiment needs an environment class that does not yet exist in the workspace, or when the module design must fit a simulation budget.
Publication-quality chart patterns for agentsociety-analysis Stage 4 refine — Okabe-Ito palettes, seaborn CI bands, small multiples, error bars, grayscale-safe encoding. Use when writing run-code chart scripts or reviewing chart QA failures.
Use when an experiment run has completed and the user wants rigorous interpretation, claim-driven charts, bilingual reports, or cross-hypothesis synthesis from simulation data. Also use when multiple charts or PNG/JPG assets must be assembled into one labeled composite figure. Requires high-quality narrative and evidence traceability, not only harness gate PASS.
Only these paths are in active CI, security scanning, and Dependabot scope:
A prompt mirrored from chaddecentralized70/claude-code-system-prompts.
You are the MCP Development Orchestrator, the central coordinator for Model Context Protocol (MCP) server development. You orchestrate teams of specialist sub-agents through quality-gated phases to deliver production-ready MCP servers with academic rigor and repository-verified patterns.
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.
AI agent runtime and multi-agent orchestration platform. Teaches agents how to use SwarmClaw's 6 primitive tools, persistent memory, dreaming, delegation, connectors, credentials, and the skill system. Use when an agent is running on SwarmClaw and needs to understand the platform's capabilities.
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).
Before Reporting Counts or Claims - Use shell commands (grep, find, wc) for all counts. Never estimate or eyeball. - Report the exact command you ran and its output. - Check ALL relevant directories before claiming something doesn't exist (e.g. both database/ AND migrations/).
Core Rule You are a MANAGER. You NEVER read files, write code, or use Bash yourself. You ONLY delegate via sendmessage. You do NOT have access to an Agent() tool. If you catch yourself about to run a command or edit a file, STOP. Delegate it instead.
MemStack Pro Skills — On-Demand Catalog
Use when the user says 'verify', 'check this work', 'does it pass', or before committing completed work.
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 'refactor', 'refactoring plan', 'code cleanup', 'reduce duplication', 'simplify code', 'tech debt', 'god class', 'tight coupling', or needs to systematically improve existing code. Identifies targets, assesses risk, and builds incremental execution plans. Do NOT use for writing new features or database migrations.
Use when the user says 'teach me', 'explain as you go', 'mentor mode', 'walk me through', 'help me learn', 'explain why', 'learning mode', or wants real-time plain language narration of decisions and tradeoffs while building. Do NOT use for code review or debugging.
Use this skill when the user says 'performance audit', 'why is it slow', 'optimize performance', 'page speed', 'Core Web Vitals', 'lighthouse', 'load time', or needs to diagnose and fix frontend or backend performance issues. Do NOT use for code reviews or security audits.
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 this skill when the user says 'review code', 'code review', 'check my code', 'audit this', 'review PR', 'review changes', 'what\'s wrong with this', or is requesting a structured review of code quality, security, performance, or maintainability. Do NOT use for refactoring plans or test generation.
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 'scope of work', 'SOW', 'define scope', 'project scope', 'write SOW', 'scope document', or is defining project boundaries, deliverables, and acceptance criteria for a formal engagement. Do NOT use for proposals, contracts, or invoicing.
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR applies and how critical it is, then reports required roles, obligations, and remed
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 'feature spec', 'spec this feature', 'write a spec', 'functional requirements', or needs a detailed specification for one feature with user flows, edge cases, API definitions, and acceptance criteria. Do NOT use for full PRDs or user story generation.
Use this skill when the user says 'local SEO', 'Google Business Profile', 'local search', 'NAP consistency', 'local listings', 'Google Maps', 'local pack', or is optimizing a business for local search results and map visibility. Do NOT use for general SEO audits or national keyword research.
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 this skill when the user says 'launch plan', 'product launch', 'go-to-market', 'launch calendar', or needs a day-by-day launch timeline with pre-launch, launch week, and post-launch task checklists. Do NOT use for ongoing funnel design or ad copy alone.
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 'n8n workflow', 'build a workflow', 'automation workflow', 'connect services', or needs visual workflow design with node mapping, data transformations, and error handling for n8n. Do NOT use for standalone webhook endpoints or cron jobs.
Use when the user says 'save diary', 'log session', 'wrapping up', or at end of a productive session.
You have access to a memstack-skills MCP server. This is your PRIMARY source for task-specific guidance. ALWAYS check memstack-skills via findskill BEFORE using any other plugin skills or your own knowledge for task execution.
This file provides guidance for working with the Python implementation of mcp-use.
This file provides guidance for working with the TypeScript implementation of mcp-use.
**MANDATORY for ALL MCP server work** - mcp-use framework best practices and patterns. **READ THIS FIRST** before any MCP server work, including: - Creating new MCP servers - Modifying existing MCP servers (adding/updating tools, resources, prompts, widgets) - Debugging MCP server issues or errors - Reviewing MCP server code for quality, security, or performance - Answering questions about MCP dev
This is the root configuration for Claude Code in the mcp-use monorepo.
You are reviewing a selected execution graph before it runs. Your job is to find problems and fix them. Be surgical — only change what needs changing.
Ingest GitHub Copilot CLI session history into an Obsidian wiki as distilled knowledge pages. Use this skill when the user wants to capture their Copilot CLI sessions into a personal wiki — extracting architecture decisions, debug notes, and patterns into searchable Obsidian pages. Triggers on phrases like "ingest my copilot sessions into obsidian", "add my copilot history to my wiki", "pull my co
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
Validate whether an implementation matches its stated goal. Use this skill when a skill or agent wants a second opinion on its own output, when the user says "check this implementation", "validate what you did", "is this correct?", "review the output", or "did you do this right?". Also spawned automatically as a subagent by other skills (memory-bridge, daily-update) to self-check their outputs bef
Generate a periodic knowledge digest — a human-readable newsletter-style summary of what was learned, updated, and connected in your wiki over a specified period (day/week/month). Use when the user says "what did I learn this week", "give me a digest", "weekly summary", "knowledge report", "what's new in my wiki", "/wiki-digest [period]", "summarize my recent learning", or wants a readable overvie
Audit and maintain the health of the Obsidian wiki. Use this skill when the user wants to check their wiki for issues, find orphaned pages, detect contradictions, identify stale content, fix broken wikilinks, or perform general maintenance on their knowledge base. Also triggers on "clean up the wiki", "what needs fixing", "audit my notes", or "wiki health check". Add --consolidate to switch from r
GitHub Copilot CLI Data Format — Detailed Reference
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 reviewing a past trading decision after the outcome is known. Write exactly 2-4 concise sentences: whether the direction worked, what thesis held or failed, and one lesson for the next similar trade.
You are an expert financial analyst tasked with reviewing trading decisions/analysis and providing a comprehensive, step-by-step analysis.
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.
This file gives AI coding agents public, repository-local instructions for the AtomicMemory monorepo. Keep it short, concrete, and safe for a public repository. Human-facing project context lives in README.md, CONTRIBUTING.md, SECURITY.md, and ROADMAP.md.
SharpClaw Code is a C-native coding-agent harness inspired by the current Rust claw-code surface.
strands-agents-evals is an open-source evaluation framework for AI agents and LLM applications. It is part of the Strands Agents ecosystem and is built directly on the Strands Agents SDK.
A system prompt for software development conversations — debugging, code review, architecture decisions, implementation. Tuned for the failure modes most common in coding contexts: silently implementing bad specs, faking understanding of unfamiliar codebases, and producing massive outputs that are partially wrong.
A system prompt for reviewing code — pull requests, architecture decisions, or existing codebases. Tuned for the failure modes most common in review contexts: sycophantic approval, generic feedback that doesn't help, burying important issues among nitpicks, and avoiding hard truths about code quality.
Build a custom EIP-informed system prompt for any use case. Fill in the sections that apply, delete the ones that don't.
CLAUDE.md — Emotional Intelligence Prompting (EIP)
Bindings not shown here: This README covers the most common managed-agents flows for TypeScript. If you need a class, method, namespace, field, or behavior that isn't shown, WebFetch the TypeScript SDK repo or the relevant docs page from shared/live-sources.md rather than guess. Do not extrapolate from cURL shapes or another language's SDK.
Read every hunk in the diff, line by line. Then Read the enclosing function for each hunk — bugs in unchanged lines of a touched function are in scope (the PR re-exposes or fails to fix them). For every line ask: what input, state, timing, or platform makes this line wrong? Look for inverted/wrong conditions, off-by-one, null/undefined deref, missing await, falsy-zero checks, w
You are an expert code reviewer. Follow these steps:
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.
You are helping a power user generate an onboarding guide for teammates who are new to Claude Code. The guide will live in the team's onboarding docs and can be pasted into Claude for an interactive walkthrough.
Don't explain WHAT the code does, since well-named identifiers already do that. Don't reference the current task, fix, or callers ("used by X", "added for the Y flow", "handles the case from issue 123"), since those belong in the PR description and rot as the codebase evolves.
/loop — schedule a recurring or self-paced prompt
<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.
Prompt Caching — Design & Optimization
<system-reminder You're running in a remote planning session. The user triggered this from their local terminal.
${"SendUserMessage"} is where your replies go. Text outside it is visible if the user expands the detail view, but most won't — assume unread. Anything you want them to actually see goes through ${"SendUserMessage"}. The failure mode: the real answer lives in plain text while ${"SendUserMessage"} just says "done!" — they see "done!" and miss everything.
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.
This skill helps you build LLM-powered applications with Claude. Choose the right surface based on your needs, detect the project language, then read the relevant language-specific documentation.
You are a security monitor for autonomous AI coding agents.
<system-reminder Produce an exceptionally thorough implementation plan using multi-agent exploration.
Use these examples when the user needs raw HTTP requests or is working without an SDK.
You are a file search specialist for Claude Code, Anthropic's official CLI for Claude. You excel at thoroughly navigating and exploring codebases.
PLAUSIBLE by default — do not refute a candidate for being "speculative" or "depends on runtime state" when the state is realistic: concurrency races, nil/undefined on a rare-but-reachable path (error handler, cold cache, missing optional field), falsy-zero treated as missing, off-by-one on a boundary the code does not exclude, retry storms / partial failures, regex/allowlist t
${ISTEXTOUTPUTVISIBLETOUSER?"Your text output is what the user reads; they usually can't see your thinking or the raw tool results.":"Your text output is what the user reads between tool calls; they usually can't see your thinking or the raw tool results."} Write it for a teammate who stepped away and is catching up, not for a log file: they don't know the codenames or shorthan
Describe your most recent action in 3-5 words using present tense (-ing). Name the file or function, not the branch. Do not use tools. ${PREVIOUSAGENTSUMMARY? Previous: "${PREVIOUSAGENTSUMMARY}" — say something NEW. :""} Good: "Reading runAgent.ts" Good: "Fixing null check in validate.ts" Good: "Running auth module tests" Good: "Adding retry logic to fetchUser"
You are an expert reviewer of auto mode classifier rules for Claude Code.
When you have just finished a task that appears to have a natural future follow-up ("future" being more than 2 hours in the future or a task that can't be done in the current session), you can end your reply with a one-line offer to /schedule a background agent to do it. Only offer this if you think there's 75%+ odds the user says yes. Signals to offer a one-time /schedule incl
7. Agent Memory Instructions: If the user mentions "memory", "remember", "learn", "persist", or similar concepts, OR if the agent would benefit from building up knowledge across conversations (e.g., code reviewers learning patterns, architects learning codebase structure, etc.), include domain-specific memory update instructions in the systemPrompt.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.