Results for “upstream”

Vendor (copy-import) a single external Claude Code skill into your own skills repo correctly — with license compliance and full provenance/attribution. Deterministic, idempotent primitive: given an upstream ref (owner/repo/path@sha or a GitHub URL) it fetches the skill, detects and gates on the license, copies the folder, injects a provenance frontmatter block (license + metadata: author/source/upstream_commit/vendored_at/provenance), ships the upstream LICENSE, adds a ## Credits section, and records a CREDITS.md ledger entry. Use when the user asks to "vendor a skill", "import a skill", "clone a skill", "borrow someone's skill", "add an external skill with attribution/credit", or スキルを取り込む / vendoring / 他人のスキルを自分のリポに取り込む. This is the import primitive that a skill-scout/curator orchestrator calls; it does NOT discover or evaluate — it correctly imports ONE skill you already chose.

The English summary is being prepared. Showing the original description.

Guide an iterative review of a built interface against its design brief, using critique and adjustment to improve visual alignment. This catalogue entry points agents to the upstream workflow, which requires a separate installation.

• Review a built interface against its design brief
• Refine visual differences through repeated adjustments
• Plan a design-to-code review cycle

Bring a Remotion branch up to date with the official main branch while preserving local changes and published history. Handle temporary change storage, merges, conflicts, validation, and a normal push when requested.

• Merge the latest main into a feature branch
• Fast-forward a local main branch
• Update a pull request branch while preserving published history

Investigate active macOS connection failures without changing network settings. Uses built-in tools to distinguish local network, DNS name lookup, upstream path, and application problems, then reports evidence, confidence, and the next useful diagnostic check.

• Investigate API or MCP service timeouts
• Check failed or inconsistent DNS lookups
• Locate likely causes of video call lag

Integrate or upgrade cache-dit in SGLang diffusion, the image generation system. Follow guidance for resolving code conflicts, adding cache settings, testing feature combinations, and comparing generated images using quality measurements and logs.

• Upgrading cache-dit in SGLang diffusion
• Resolving conflicts when porting upstream changes
• Adding per-request cache settings

Upgrade a customized NanoClaw installation by recording changes in a reusable migration guide and reapplying them to a clean upstream version. The workflow includes backups, validation in a separate working directory, and rollback instructions.

• Upgrade NanoClaw while preserving custom settings and code
• Document customizations in a reusable migration guide
• Validate an upgrade in a separate working directory

Guide changes to Ghostty within cmux, including optimized GhosttyKit builds and upstream updates. Defines how to publish submodule commits, update the parent repository’s reference, and document fork changes so future checkouts can retrieve the required code.

• Rebuilding GhosttyKit after changes
• Bringing upstream Ghostty updates into a fork
• Updating the parent repository’s submodule reference

Audit npm, PyPI, and Go dependencies for version-specific advisories, inactive upstream projects, concentrated npm publishing rights, and installation scripts. Produce a report backed by collected data, with assessment coverage, action priorities, and upgrade or replacement guidance.

• Reviewing dependency risks before an engagement
• Checking advisories across a lockfile dependency tree
• Finding abandoned or archived dependencies

Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs. Opens a fork PR only for upstream openai/codex; LazyCodex-owned defects become a verified-fix issue on code-yeongyu/lazycodex (never a PR — that repo is a generated distribution mirror). Use when the user asks to fix a bug, contribute a bug fix, contribute to fix bug, open a PR for a bug, or debug and PR a LazyCodex/Codex defect.

The English summary is being prepared. Showing the original description.

Research and prepare an outside contribution to an open-source repo, then stop at a queue item for a human to approve: policy check, intake, duplicate check, reproduction, patch, the repo's own checks, an independent critic rerun, and a disclosed, hashed draft of the exact text to post. Use this skill whenever the user wants to contribute to someone else's repo, fix an upstream bug, pick up a good-first-issue, draft an AI-assisted pull request for an outside project, follow up on their own outside PR, or run a gated contribution pipeline. Triggers on open source contribution, contribute to this repo, upstream fix, outside PR, external PR, good first issue, fix this issue in their repo, contribution research, AI-assisted PR, disclose AI in PR, reply to review on my PR. Also triggers when the user names an issue in a repo they do not maintain and asks for a fix, even if they do not say contribute.

The English summary is being prepared. Showing the original description.

Run upstream brand discovery covering audience research, competitive landscape, category dynamics, problem space, and positioning territory exploration. Use this skill at the very start of a brand or website project when the user needs to understand who they're for, who they compete with, what the audience actually needs, and where the brand could plausibly stand. Triggers on brand discovery, audience research, market research, competitive scan, category research, customer research, who is this for, who are we, positioning research, intake, kickoff. Also triggers when a creative brief is requested but the upstream inputs (audience, competitors, problem space) are not yet clear.

The English summary is being prepared. Showing the original description.

Improve an open-source GitHub skill and open a friendly suggestion PR upstream: fork, run skill-creator's retrofit, attach asm eval before/after metrics. Don't use for local-only skills, authoring from scratch, bulk repos, or registry publish.

The English summary is being prepared. Showing the original description.

Help the user turn their Retentioneering ideas, friction reports, bug findings, or feature needs into high-quality upstream contributions: from capturing and validating the idea, through minimal reproductions and issue drafts, to preparing, testing, and submitting a pull request that follows this repository's conventions. Use when the user says they found a bug, wants a feature, wrote a workaround worth upstreaming, or asks how to contribute, open an issue, or make a PR to retentioneering-tools.

The English summary is being prepared. Showing the original description.

Use when installing a model family from an installer pack, or when building/deriving a new pack from an upstream installer or a workflow JSON. Explains the manifest-driven packs/ system and tells you to invite the user to contribute new packs back upstream.

The English summary is being prepared. Showing the original description.

Pointer to the upstream skill for building voice agents with speech-to-speech and STT-LLM-TTS pipelines, installed from upstream.

The English summary is being prepared. Showing the original description.

Pointer to the upstream skill for React and Next.js performance work (data fetching, bundle size, re-renders), installed from upstream.

The English summary is being prepared. Showing the original description.

Pointer to the upstream skill for behavioural guidelines that reduce common LLM coding mistakes, installed from upstream.

The English summary is being prepared. Showing the original description.

Pointer to the upstream skill for writing PRDs grounded in the existing repo, with a fixed output folder, installed from upstream.

The English summary is being prepared. Showing the original description.

Propose a turbo skill improvement upstream by filing a GitHub issue against the turbo repo. Use when the user asks to "contribute to turbo", "submit turbo changes", "contribute back", "suggest a turbo improvement", or "upstream my changes".

The English summary is being prepared. Showing the original description.

Use when event content or site changes are finished and need to reach devopsdays.org - covers branching, rebasing on upstream main, local preview, committing, pushing to a fork or to upstream, opening the pull request, and interpreting a failing check.

The English summary is being prepared. Showing the original description.

Review and upgrade MetaX model support against a target vLLM revision and installed MACA components, recursively including model-dependent attention and kernels. Establish quantization and cache differences, preserve upstream structure, and distinguish shared upstream bugs from adaptation defects. Use for model support work, not standalone monkey-patch or registry audits.

The English summary is being prepared. Showing the original description.

Pull structural updates from upstream ObsidianOS into the local vault.

The English summary is being prepared. Showing the original description.

Sync a skill's content against the upstream library it covers — check whether the API descriptions, version references, and SOURCE: citations inside SKILL.md and its reference files still reflect what the library actually does today. Use when a library has released updates that may have changed the APIs the skill covers, when a skill references an old library version, when asked to sync, refresh, update, or check a skill against upstream docs, when the skill's content may have drifted from current library behavior, or when SOURCE: citations are stale. Accepts a SKILL.md path, skill directory, or plugin directory.

The English summary is being prepared. Showing the original description.

Safely sync navigator's agent-browser fork with upstream vercel-labs/agent-browser, analyze changes, and generate integration documentation

The English summary is being prepared. Showing the original description.