Results for “package-code”

Turn raw MATLAB code into a published .mltbx toolbox — full pipeline from scope definition through packaging and release. Drives 8 phases with human checkpoints, enforcing ordering and dependencies. Use when asked to package, create a toolbox, or run the files-to-package pipeline.

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

Audit project dependencies for risk — known-vulnerable versions, unpinned ranges, abandoned packages, and badly outdated majors. Reads package.json, requirements.txt, go.mod, Cargo.toml. Pure Claude Code, no signup.

Localize VS Code extensions including configurations, walkthroughs, and source code messages following official guidelines.

Create, repair, validate, and package Codex-compatible animated pets and spritesheets from character art, brand cues, or reference images.

Index and search code repositories, documentation, research papers, HuggingFace datasets, local folders, and packages via the Nia API, with AI-powered research and code advisor capabilities.

Guides the agent to research existing tools, libraries, and patterns before writing custom code, using parallel searches across package registries, MCP servers, skills, and GitHub, then evaluating and deciding to adopt, extend, or build.

Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python code.

Provides idiomatic Go patterns, best practices, and conventions for writing, reviewing, and refactoring Go code.

Check dependency licenses against your project's license and flag conflicts, copyleft obligations, and unknown/unlicensed packages. Reads manifests directly. Advisory, not legal advice. Pure Claude Code, no signup.

Migrates .NET test projects from xUnit.net v2 to xUnit.net v3, updating package references, project files, and code to compile and pass tests.

Scaffold, build, and package SwiftPM-based macOS apps without an Xcode project, including custom .app bundle assembly, signing, notarization, and appcast generation.

Find and fix vulnerabilities in code and dependencies with Snyk. Use when a user asks to scan for security vulnerabilities, audit npm packages, check Docker images for CVEs, or integrate security into CI/CD.

Provides file paths to language-specific extension files for the code-testing pipeline, enabling discovery of guidance for .NET, Python, TypeScript, and other languages.

Creates CodeTour .tour files — persona-targeted, step-by-step walkthroughs that link to real files and line numbers for any repository.

Use ONLY for code review and test write/review guidance in `packages/agent-core-v2` (the DI × Scope agent engine). Does NOT apply to the legacy `packages/agent-core` or to any other package — for those, do not load this skill. Groups the review and testing lenses used for agent-core-v2 — `slop` (single-level-of-abstraction / layered error-handling review, invoked only on explicit request) and `test` (contract-driven per-test rules for both authoring and reviewing tests). Apply the sub-skill that matches the task; do not apply `slop` unprompted.

Sign build artifacts (binaries, packages, containers) with GPG, Sigstore, and platform-specific tools to ensure integrity and authenticity throughout the software supply chain.

Load this skill when the user says "update coding standards", "update-coding-standards", or "/update-coding-standards". Analyzes the diff of a merged PR and appends any valuable new patterns to the relevant coding standards doc — but only if something genuinely warrants documenting.

This skill embodies the principles of "Clean Code" by Robert C. Martin (Uncle Bob). Use it to transform "code that works" into "code that is clean."

Build a task-aware context bundle (relevant code + applicable standards + related past decisions) via the local RAG index, capped at a token budget. Use at the start of any implementation/refactor/debug task instead of reading files blindly. Replaces "read whole file" with "retrieve the function + callers + rules + prior ADR."

Guides code modifications by reading affected files first, matching existing style, and making minimal, safe changes.

Scan for unused exports, unreachable code, orphaned files, and stale dependencies

Inspect package metadata, lockfiles, scripts, and npm release readiness.

Find dead code in a repo — unused exports, unreferenced files, unreachable branches, unused imports, and declared-but-unused dependencies. Reports each with file:line and a safe-to-remove confidence. Pure Claude Code, no signup.

Review and refactor code according to project-specific coding guidelines and instructions.

Packages an existing talking-head, interview, or podcast video with timed, designed graphic overlay cards—kinetic titles, lower-thirds, data callouts, quotes, side panels, picture-in-picture—synced to the transcript, on a 16:9, 9:16, or 4:5 canvas.

Creates persona-targeted, step-by-step CodeTour walkthroughs that link to real files and line numbers for onboarding, architecture, PR review, and more.

Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.

GSD Execute — Get Shit Done

Code Cleanup