Multi Repo Setup

Set up a cross-repo investigation when a workload from another repo (pypto, pypto-lib, pypto-serving, etc.) needs to be run, especially when you want to swap in simpler-main HEAD or the current worktree's simpler instead of the version that repo pins. Documents the repo graph (who imports who), clones-or-updates each external repo every invocation so stale local clones don't lie about CI parity, and points at each repo's own skills/docs for workload-specific steps. MUST invoke before chasing "X doesn't work on simpler" reports where X lives outside this repo.

49 stars 102 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add hw-native-sys/simpler --skill multi-repo-setup
Manual install
git clone --depth 1 https://github.com/hw-native-sys/simpler.git /tmp/simpler
mkdir -p ~/.claude/skills
cp -r /tmp/simpler/.claude/skills/multi-repo-setup ~/.claude/skills/multi-repo-setup

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Multi-Repo Investigation Setup

This skill answers one question: **given a workload that lives in another
repo, how do the repos relate, and how do I clone + set up each one so the
workload runs against the simpler I want?** It stops at "the repos are
installed and the workload's own entry point is reachable" — for what to
*run* and how to read its output, defer to that repo's own skills/docs
(see [Step 5](#step-5-hand-off-to-each-repos-own-skillsdocs)) or, for the
qwen3 workload specifically, to
[`multi-repo-qwen-setup`](../multi-repo-qwen-setup/SKILL.md).

The skill lives in the simpler repo, so `$PWD` when you invoke it is
already a simpler worktree — nothing to clone for simpler itself. Every
other repo gets cloned-or-updated to a canonical local path each time. The
default is to follow each repo's own pinning. Simpler dev often diverges
from that to swap in either simpler-main HEAD or the current worktree.

## When to invoke

Invoke before:

- running an external-repo workload (`python <ext>/some_test.py`,
  pytest in another repo, etc.) for the first time in a session, or
- reporting "X doesn't work on simpler" where X lives in another repo.

Skip for work that stays inside `simpler/` (its own pytest, examples,
unit tests).

## Step 1: The repo graph (who imports who)

For an Ascend workload investigation, the cast is usually some subset
of these. `simpler` is `$PWD` — the other repos are cloned under the
Read the full skill on GitHub

Details

Skill name
multi-repo-setup
Path
.claude/skills/multi-repo-setup/SKILL.md
Repo updated
18 November 2026

FAQ

What does the Multi Repo Setup skill do?

Set up a cross-repo investigation when a workload from another repo (pypto, pypto-lib, pypto-serving, etc.) needs to be run, especially when you want to swap in simpler-main HEAD or the current worktree's simpler instead of the version that repo pins. Documents the repo graph (who imports who), clones-or-updates each external repo every invocation so stale local clones don't lie about CI parity, and points at each repo's own skills/docs for workload-specific steps. MUST invoke before chasing "X doesn't work on simpler" reports where X lives outside this repo.

How do I install the Multi Repo Setup skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add hw-native-sys/simpler --skill multi-repo-setup. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Multi Repo Setup popular?

It lives in hw-native-sys/simpler, which has 49 GitHub stars and 102 forks.

Related skills

Benchmark

49

hw-native-sys/simpler

Benchmark runtime performance on hardware. If the current branch has commits ahead of upstream/main or uncommitted changes, compares against the fork point (merge-base). Otherwise benchmarks current state only. Use when the user asks to benchmark, measure performance, or compare latency.

Git & Code Review102

Checkout PR

49

hw-native-sys/simpler

Add a remote for a given PR's head repository and checkout a local pr-xxx-work branch. Use when the user wants to work on someone else's PR locally.

Git & Code Review102

Clean Branches

49

hw-native-sys/simpler

Remove stale local and remote git branches that have been merged into main. Detects regular merges and squash merges. Cleans up fork remote branches and prunes tracking refs. Use when the user asks to clean up branches, remove merged branches, or tidy up git.

Git & Code Review102

Process Issue

49

hw-native-sys/simpler

Process a GitHub Issue as a maintainer, from triage and ownership routing through dependencies and evidence-based closure. Use to manage an Issue's next step; use fix-issue for implementation.

Git & Code Review102

Multi Repo Qwen Setup

49

hw-native-sys/simpler

Concrete qwen3-14B guide on NPU against the current worktree's simpler. Points at simpler's own in-repo qwen3_14b_decode example (zero cross-repo), then covers the two cross-repo paths — the pypto-serving runner (prefill/decode TPOT) and the pypto-lib decode_fwd kernel (device decode TPOT + scheduler DFX). Defers cross-repo clone/install to multi-repo-setup, then gives the exact run commands (batch-1 and batch-16), the prefill ring/timeout gotchas that otherwise surface as 507018, how to read the per-token timing layers, and the kernel-level device-timing / swimlane flow. Invoke when running q

Git & Code Review102

Process PR

49

hw-native-sys/simpler

Process a GitHub PR as a maintainer, routing review, following revisions, checking merge readiness and reconciling linked Issues. Use for PR lifecycle management; use review-pr for technical review and fix-pr for author-side repairs.

Git & Code Review102

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.