gh-address-comments

IronSyd

Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.

notion-research-documentation

IronSyd

Research across Notion and synthesize into structured documentation; use when gathering info from multiple Notion sources to produce briefs, comparisons, or reports with citations.

sentry

IronSyd

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.

database schema and migrations

IronSyd

Plan database schema evolution, migration rollout, backfills, and rollback. Use when introducing schema changes, data transformations, or compatibility-sensitive DB updates.

doc

IronSyd

Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.

prd-scope-and-acceptance

IronSyd

Define product requirement documents, scope boundaries, acceptance criteria, and non-goals. Use when starting a new feature, planning a roadmap item, or turning ideas into implementation-ready specs.

test-strategy-unit-integration-e2e

IronSyd

Define a risk-based testing strategy across unit, integration, and end-to-end layers. Use when planning quality gates for new features, refactors, releases, or CI policy changes.

Notion Meeting Intelligence

IronSyd

Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.

security-threat-model

IronSyd

Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.

system-architecture-and-adrs

IronSyd

Design system architecture and create ADRs for critical technical decisions. Use when introducing new services, changing system boundaries, selecting infrastructure patterns, or documenting high-impact tradeoffs.

Figma: Implement Design

IronSyd

Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.

playwright

IronSyd

Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.

api-contracts-and-versioning

IronSyd

Define and review API contracts, compatibility rules, and versioning strategy. Use when creating new endpoints, changing request/response schemas, or planning deprecations.

Render Deploy

IronSyd

Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use this skill when the user wants to deploy, host, publish, or set up their application on Render's cloud platform.

Linear

IronSyd

Manage issues, projects, and team workflows in Linear. Use when the user wants to read, create, or update tickets in Linear.

security-best-practices

IronSyd

Perform language- and framework-specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best-practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (Python, JavaScript/TypeScript, Go). Do not trigger for general code review, debugging, or non-security tasks.

openai-docs

IronSyd

Use when a user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations (for example: Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, model capabilities or limits). Prioritize the OpenAI developer docs via the MCP tools and restrict any fallback browsing to official OpenAI domains.

screenshot

IronSyd

Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.

imagegen

IronSyd

Use when the user asks to generate or edit images via the OpenAI Image API (for example: generate image, edit/inpaint/mask, background removal or replacement, transparent background, product shots, concept art, covers, or batch variants); run the bundled CLI (scripts/image_gen.py) and require `OPENAI_API_KEY` for live calls.

project-specification

IronSyd

Force decision-complete planning before any mutating implementation work. Use for all coding tasks that could modify files, schemas, configs, migrations, infrastructure, deployments, or runtime behavior.

Notion Knowledge Capture

IronSyd

Capture conversations and decisions into structured Notion pages; use this when turning chats or notes into wiki entries, how-tos, decisions, or FAQs with proper linking.

Notion Spec to Implementation

IronSyd

Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans and tasks from them.

gh-fix-ci

IronSyd

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

Incident and Postmortem

IronSyd

Run incident response and produce actionable postmortems. Use when triaging outages, coordinating mitigation, documenting root cause, and assigning follow-up actions.

release-and-rollback-runbook

IronSyd

Build release plans and rollback runbooks for production changes. Use when preparing deployments, approving go-live, or reducing release risk for critical updates.