원클릭으로 Manus에서 모든 스킬 실행

spm-package-audit

스타0

포크0

업데이트2026년 5월 5일 17:02

Audits and automatically fixes Swift Package Manager library packages. Removes Package.resolved from git tracking, ensures the sibling dependency pattern is in place via /toggle-sibling-libraries, and bumps every intrusive-memory/* dep to its latest published release. Explicitly invoked only — does not auto-trigger.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

intrusive-memory

intrusive-memory/package-collection

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

SPM Package Audit

Run on a Swift Package Manager library on the development branch when you want to refresh package hygiene before continued work or before invoking /ship-swift-library. Two responsibilities:

Package.resolved tracking — libraries should not check this in. If it is tracked, remove it and add to .gitignore.
intrusive-memory/ version currency* — bump every intrusive-memory/* dep currently in the sibling pattern to its latest published GitHub release.

The state of the sibling pattern itself (helper functions, useLocalSiblings, sibling vs. direct .package(url:) calls) is delegated to /toggle-sibling-libraries. This skill no longer rewrites that scaffolding directly — keeping a single source of truth for the toggle prevents the two skills from drifting.

When to use

Tidy up a development branch before /ship-swift-library.
Pull in newly-released intrusive-memory deps without going through a full ship cycle.
Restore Package.swift to the canonical sibling shape after manual edits.

Do not use for: Xcode app projects, non-Swift packages, or packages with no intrusive-memory/* dependencies.

Procedure

Run these in order. Each is idempotent.

1. Confirm we're in an SPM library

test -f Package.swift || { echo "ABORT: not in an SPM package directory"; exit 1; }

If Package.swift declares only .executable products and no .library, this skill does not apply (executables ship Package.resolved on purpose). Surface that and ask the user before continuing.

2. Package.resolved audit

if [ -f Package.resolved ] && git ls-files --error-unmatch Package.resolved >/dev/null 2>&1; then
  git rm --cached Package.resolved
  grep -qxF 'Package.resolved' .gitignore 2>/dev/null \
    || printf '\nPackage.resolved\n' >> .gitignore
  echo "Removed Package.resolved from git tracking, added to .gitignore."
else
  echo "Package.resolved not tracked — nothing to do."
fi

The Package.resolved file is still useful locally (SPM keeps writing it); we just don't want it under version control for libraries because consumers should resolve their own pins.

3. Ensure Package.swift is in sibling mode

Hand off to the dedicated toggle skill — it owns the helper-function + scaffolding rewrite and is byte-stable / idempotent:

/toggle-sibling-libraries --to sibling

What this guarantees on return:

import Foundation and import PackageDescription present in the canonical order.
The useLocalSiblings constant and both sibling(...) helper functions present in their canonical form.
Every .package(url: "https://github.com/intrusive-memory/<repo>.git", .upToNextMajor(from: "X.Y.Z")) rewritten to sibling("<repo>", remote: "...", from: "X.Y.Z").
Non-intrusive-memory deps untouched.

If Package.swift was already in sibling state, the toggle reports a no-op and returns success.

4. Bump intrusive-memory/* versions to latest

For each sibling("<Repo>", remote: "https://github.com/intrusive-memory/<Repo>.git", from: "X.Y.Z") call in Package.swift, look up the latest released tag and edit from: if it differs:

# Extract the repo names that are currently in sibling form
REPOS=$(grep -oE 'sibling\("[A-Za-z0-9_-]+",' Package.swift | sed -E 's/sibling\("([^"]+)",/\1/' | sort -u)

for repo in $REPOS; do
  latest=$(gh api "repos/intrusive-memory/${repo}/releases/latest" --jq '.tag_name' 2>/dev/null | sed 's/^v//')
  if [ -z "$latest" ]; then
    # Fall back to most recent vX.Y.Z tag
    latest=$(gh api "repos/intrusive-memory/${repo}/tags" \
      --jq '[.[].name | select(test("^v[0-9]+\\.[0-9]+\\.[0-9]+$"))][0]' 2>/dev/null | sed 's/^v//')
  fi
  if [ -z "$latest" ] || [ "$latest" = "null" ]; then
    echo "WARNING: no published release for intrusive-memory/${repo} — leaving version as-is"
    continue
  fi
  echo "intrusive-memory/${repo} -> ${latest}"
done

For each repo whose latest version differs from what Package.swift currently has, use the Edit tool to change just that from: line. Pattern (the sibling( block spans multiple lines):

sibling(
  "<Repo>",
  remote: "https://github.com/intrusive-memory/<Repo>.git",
  from: "<old>")

→ change <old> to <latest>. Don't rewrite the surrounding lines or whitespace; the toggle in step 3 already produced canonical formatting.

5. Verify and report

swift package resolve 2>&1 | tail -5

If resolve fails, surface the error. Otherwise emit a short summary:

## SPM Package Audit Complete

### Package.resolved
- Status: [removed | already clean | not present]

### Package.swift sibling pattern
- Status: [restored | already in sibling mode]

### Versions bumped
| Dependency  | Old    | New    |
|-------------|--------|--------|
| SwiftBruja  | 1.6.1  | 1.7.0  |
| SwiftAcervo | 0.11.0 | 0.11.1 |

(or "All intrusive-memory/* deps already at latest published versions.")

Do not commit on the user's behalf — the audit's output usually rolls into a larger commit (either a routine dev-branch tidy or as part of /ship-swift-library Step 3). The user controls when to commit.

Error handling

No intrusive-memory/* deps: skip steps 3 and 4, run only the Package.resolved audit, and note that nothing else applied.
gh not authenticated or offline: report and skip step 4 (the version bump). Do NOT skip step 3 — the toggle's --to sibling direction does not need network access (it doesn't resolve versions, just preserves the existing from: values).
gh api returns no releases for a repo: leave that dep at its current version and warn. The user may need to publish a release for that upstream first.

Notes

The sibling pattern lets local ../SwiftBruja, ../SwiftAcervo, etc. checkouts override the remote pin during development; CI always uses the pin because useLocalSiblings is false when CI=true.
The toggle skill (/toggle-sibling-libraries) is the single source of truth for the helper-function shape — if the canonical form ever changes, update that skill rather than this one.
Steps in this skill are deliberately not parallelized into subagents; the work is small and sequential dependencies (toggle must run before version bumps so the regex in step 4 finds the sibling( blocks) make subagent orchestration overkill.

이 저장소의 다른 Skills

같은 저장소

ship-app

intrusive-memory/package-collection

Ship one or more iOS/macOS App Store apps from a single repo through development → main → TestFlight, then promote to the App Store by tagging a release candidate (v<version>-rc.<k>) on main and merging that tag into a release branch. Handles repos that ship several apps at once (e.g. an iOS app + a macOS app, each its own App Store Connect record/scheme). Orchestrates the development→main PR cycle (which auto-ships to TestFlight via Xcode Cloud), then the RC-tag → release promotion that uploads to App Store Connect, then submission. Xcode Cloud only builds/archives/uploads; GitHub CI owns all test gating. Use when asked to ship, release, cut a release candidate, promote to the App Store, run release QA, or push iOS/macOS apps to TestFlight or the App Store.

2026-07-130

ship-swift-library

intrusive-memory/package-collection

Ship and release Swift library versions by bumping the version on development, merging the PR once CI passes, then tagging and creating a GitHub release from main. Accepts an optional version-bump argument (`patch`/`minor`/`major`) or explicit semver (`1.2.3`) to run unattended.

2026-07-130

test-analysis

intrusive-memory/package-collection

Audit a Swift test suite across five dimensions and produce a single markdown findings report with concrete recommendations. Run multiple passes that each look at the test suite from a different angle — repetition, superfluity, coverage gaps (using real xccov data), flaky-in-CI risk, and CI gating of performance tests. Use this skill whenever the user asks to audit, analyze, review, critique, or clean up their tests, including phrases like "test analysis", "audit my tests", "review the test suite", "are there redundant tests", "find flaky tests", "test coverage gaps", "which tests can I delete", "are my tests good", or whenever they want a holistic read on Swift test-suite health. Triggers on Swift Package Manager / Xcode projects with XCTest or swift-testing test targets. Defer to Makefile targets when present; never run `swift test` or `swift build`.

2026-06-160

codemap

intrusive-memory/package-collection

Generate or refresh a graphify knowledge-graph codemap of the current repo, gitignore the machine-specific/regenerable pieces, and commit only the portable map artifacts. Use whenever the user wants to build, update, refresh, regenerate, sync, or commit the codemap / graphify map / code graph for a project — phrases like 'update the codemap', 'refresh the graphify map', 'rebuild the code graph', 'commit the codemap', 'regenerate graphify-out', 'sync the codemap before I push', or any variation of keeping a checked-in graphify-out/ map current. Handles first-time generation and incremental updates, enforces the correct .gitignore split (absolute-path markers + cache + manifest.json stay out; graph.json/html/report stay in), untracks anything now-ignored, ensures AGENTS.md references the codemap, and makes one clean commit. Optionally pushes.

2026-06-130

create-pull-request

intrusive-memory/package-collection

Finalize the pull request for the current branch — find the existing (usually draft) PR, regenerate its title and body from the branch's commits, fix the base branch if it's wrong, and mark it ready for review. Falls back to creating a new PR only when none exists. Use this skill whenever the user asks to "create a PR", "open a PR", "make a pull request", "PR this", "send it up", "mark it ready", "ready for review", "finalize the PR", or any variation that implies promoting the current branch into review — including casual phrasings like "now PR it" or "go ahead and ship the PR". The skill picks the base branch using the project's tiered convention (mission/* → development, development → main, everything else → development), enforces standard safety checks (clean working tree, not on main, push first), and writes a Summary + Test plan body from the commits on the branch. Prefer this skill over running `gh pr create` / `gh pr ready` directly so the routing and safety rules apply consistently.

2026-05-160

mission-supervisor

intrusive-memory/package-collection

Plan and execute sorties with sergeant precision. Give each agent ONE clear, measurable goal. Pre-execution commands (breakdown, refine + 4 subcommands) create and refine an EXECUTION_PLAN.md from requirements. Refine performs 4 passes: atomicity/testability, prioritization, parallelism (up to 4 sub-agents, builds only by supervisor), and open questions. Execution commands (start, resume, status, stop, killall) orchestrate sortie agents with lean context and crystal-clear objectives. THE RITUAL (name-feature) generates humorous military operation names. Post-mission flow runs automatically after the last sortie completes: (test-cleanup) prunes tests added during the mission that cannot run reliably in CI, then (brief) harvests lessons and renders an explicit ROLLBACK | KEEP | PARTIAL_SALVAGE verdict, then auto-triggers (clean) → /organize-agent-docs to archive every mission artifact in the project root into docs/<complete|incomplete>/<mission name>/.

2026-05-130

name	spm-package-audit
description	Audits and automatically fixes Swift Package Manager library packages. Removes Package.resolved from git tracking, ensures the sibling dependency pattern is in place via /toggle-sibling-libraries, and bumps every intrusive-memory/* dep to its latest published release. Explicitly invoked only — does not auto-trigger.
allowed-tools	Bash, Read, Edit, Skill