seis-code

Implements, refactors, and validates code changes across the SEIS ecosystem.

1|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-code-emirhankudun-ux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seis-code
Source: https://github.com/emirhankudun-ux/SEIS/tree/main/plugins/seis/skills/seis-code
Command: npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-code-emirhankudun-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes in a large multi-platform ecosystem risk breaking architecture, losing user work, or skipping validation. This Skill provides a disciplined engineering lane for implementing, refactoring, debugging, and testing code inside the SEIS repository while preserving uncommitted work, main-branch safety, security, and documentation quality. ## Core Features & Use Cases - Architecture-aware implementation: Maps each change to the correct lane (Apple platforms, web, backend/API, MCP/plugin, automation, CI) before editing, using existing scripts and typed APIs instead of ad hoc patterns. - Safety-first workflow: Inspects git status, branch, and remotes first, makes the smallest durable change, and never discards uncommitted work or exposes secrets. - Validation and quality gates: Runs repo-provided checks such as npm run seis:check and package-local tests, scaling validation only when risk requires it. - Use Case: Ask the agent to fix a bug in a SEIS web surface; it reads nearby docs and manifests, makes a minimal typed change, runs the repo's check scripts, and records durable decisions in documentation. ## Quick Start Use $seis-code to implement a scoped SEIS code change safely, for example fixing a bug in the web app and validating it with the repo's check scripts.

Frequently Asked Questions about seis-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a code change safely in the SEIS repository?▼

Start by inspecting git status, branch, and remotes, then read nearby AGENTS.md, README, and package manifests before editing. Make the smallest durable change using existing scripts and typed APIs, then validate with repo commands like npm run seis:check.

What platforms and languages does SEIS code work cover?▼

It covers Apple platforms with Swift, SwiftUI, AppKit, and Xcode; web with TypeScript, React, and Next.js; backends with Node, Python, Go, Rust, and SQL; plus MCP servers, plugins, and repository automation scripts.

How are code changes validated in the SEIS ecosystem?▼

Validation uses the lightest reliable checks first, preferring repo-provided commands such as npm run seis:check, check:seis-plugin-bundle, check:seis-platform-kernel, and package-local tests, scaling up only when risk or blast radius requires it.

Does the skill protect uncommitted work and secrets during edits?▼

Yes. Guardrails prohibit discarding uncommitted changes, rewriting unrelated files, or exposing secrets, tokens, API keys, certificates, and provisioning files. GitHub, cloud, or deployment readiness is never claimed without a real local verification.

When should helper plugins like GitHub, Sentry, or Cloudflare be used?▼

Helper plugins are used only when they directly support the active task, such as GitHub and CodeRabbit for review, Sentry and Datadog for runtime evidence, or Cloudflare and Vercel for scoped cloud and backend work.