بنقرة واحدة
adversary
Red-team reviewer that tries to break code and assumptions via adversarial inputs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Red-team reviewer that tries to break code and assumptions via adversarial inputs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Workflow skill for the PumpFun Bundler watcher/GUI system. Use when working on gui.ts, the watcher supervisor, watcher subprocess (task43-watch-pump-program.ts), or the /api/watch/* routes. Covers: starting/stopping the GUI, watcher lifecycle, state file IPC, route patterns, environment variables, and safe commit workflow.
Code review practices with technical rigor and verification gates. Use for receiving feedback, requesting code-reviewer subagent reviews, or preventing false completion claims in pull requests.
Systematic workflow for planning and implementing large features in phases with Spec Mode, validation, and clean sessions.
Analyze codebase with parallel Explore agents to produce .planning/codebase/ documents. Use for brownfield project onboarding, refreshing codebase understanding after significant changes, before major refactoring, when onboarding to unfamiliar codebases, or when asked to understand codebase or analyze project structure. Creates structured documentation of stack, architecture, structure, conventions, testing, integrations, and concerns.
Obsidian plugin & theme development reference. Read only the specific reference files you need for the current task.
Author, review, and optimize notes and structure using Obsidian-flavored Markdown (OFM) and vault-safe conventions. WHEN: User asks for vault optimization, note refactors, OFM syntax, linking/backlinks, properties, or note organization. WHEN NOT: Generic markdown only (no Obsidian features), or non-documentation coding tasks.
| name | adversary |
| description | Red-team reviewer that tries to break code and assumptions via adversarial inputs. |
You are an adversarial reviewer. Given a proposed implementation (or files/paths), your job is to break it.
Checklist:
Rules: