Bring one of unional's repos or organizations up to the standard baseline — branch protection ruleset, merge and Actions settings, security toggles, and the CI/release file layout. Use when setting up a new repo, when asked to 'update branch protection',…
unional/skills
SkillsMP has collected 17 skills from unional/skills. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 17
- GitHub stars
- 0
- GitHub forks
- 0
Skills in this repository
Showing 17 of 17 collected skills.
Apply a consistent documentation standard: controlled plain prose, one home per fact, and every external claim backed by a source. Use when writing or revising documentation, READMEs, or skill bodies; when deciding where a document belongs; when moving,…
Sweep an owner's repos to find which ones stopped publishing, classify each failure by root cause, and report the evidence needed to fix them. Use when asked 'which of my repos are broken?', 'is anything not publishing?', 'audit my releases', 'find repos that…
Decide what to do with one of unional's repos still on a legacy CI shape — a single `nodejs.yml` calling `typescript-build.yml`/`typescript-test.yml`/`npm-release.yml`, or inlined yarn steps — and then archive it, drop its CI, or migrate it to the…
Bring one repo fully current: settings baseline, a release that publishes without long-lived tokens, dependency PRs that merge themselves, and proof it all works. Use this skill when asked to 'modernize this repo', 'bring it up to standard', 'fix everything…
Replace a TypeScript library's build, lint, test and dependency stack in one pass — tsdown for the build, biome for lint, turbo for tasks, vitest for tests — instead of upgrading tools that the swap deletes. Use when asked to 'modernize the toolchain', 'bring…
Move a package's release off long-lived NPM_TOKEN/PAT secrets onto OIDC trusted publishing, migrating it to pnpm + changesets on the way, and keep dependency PRs merging themselves. Use this skill when a release publishes with a token, has silently stopped…
Move a repo from a personal namespace into an organization without breaking its release — re-registers the npm trusted publisher that pins owner/repo, fixes package metadata and badges, and turns on the merge queue that only org-owned repos can have. Use when…
Add a changeset to the current change. Use when preparing a PR that affects published packages, when asked to 'add a changeset', or when CI reports a missing changeset. Detects monorepos and selects affected packages automatically.
Fix bugs without hand-holding. Investigate logs, errors, failing tests — then resolve. Zero context switching for the user. Use when given a bug report, fixing failing CI, or when the user reports an error.
Use this skill when contributing a design proposal to an open-source community — research, draft with evidence, file.
Pause on non-trivial changes to ask for a more elegant solution. Skip for simple fixes. Use when a fix feels hacky, implementing non-trivial changes, or before presenting work. Elegance for non-trivial; pragmatism for trivial.
Capture corrections in tasks/lessons.md. Update after ANY user correction, write rules to prevent repeat mistakes, review at session start. Use when receiving corrections, starting a session, or building a lessons-learned practice.
Set up changesets in a new or existing repository. Use when asked to 'add changesets', 'set up releases', or 'configure versioning'. Handles single packages and monorepos. Optionally sets up a shared reusable workflow in a <user/org>/.github repo.
Use subagents liberally for research, exploration, and parallel analysis. Offload work to keep main context clean. Use when context is crowded, tasks can run in parallel, or for research/exploration work. One focused tack per subagent.
Never claim a task complete without proving it works. Run tests, check linter, verify build. Use when finishing tasks, before marking done, or when the user asks for verification. Requires evidence for every completion claim.
Plan-first for non-trivial tasks. Enter plan mode, write to tasks/todo.md, stop and re-plan when things go sideways. Use when starting complex work (3+ steps), making architectural decisions, or before implementation.