Skip to main content
GitHub repository

skills

skills contains 6 collected skills from we-are-singular, with repository-level occupation coverage and site-owned skill detail pages.

skills collected
6
Stars
2
updated
2026-08-03
Forks
1
Occupation coverage
1 occupation categories · 83% classified
repository explorer

Skills in this repository

singular-code-review
unclassified

Use when reviewing code changes, pull requests, branches, or work-in-progress diffs for correctness, intent fit, repo-local architecture, surrounding-code pattern mismatches, maintainability, naming, tests, and over-engineering. Runs a git-heavy, subagent-oriented review that reads local AGENTS.md/docs/plans/conversation/PR context before judging the diff.

2026-08-03
git-commit-pr
software-developers

Use when preparing local changes for commit, push, and pull request creation, especially in repositories that use conventional commits, package/workspace scopes. This skill optimizes for clean history, package-scoped commits, repository-specific rules, and a PR body that explains intent.

2026-07-28
git-setup-repo
software-developers

Set up, standardize, or singularify a repository with monorepo dependency ownership, CI, Oxc, Vitest coverage, Git hooks and commit rules, workspace metadata, local services, release checks, and README onboarding. Use for new repo bootstrapping, existing repo cleanup, monorepo conversion, or dependency deduplication.

2026-07-28
git-fix-pr
software-developers

Use when an active PR needs a deliberate fix pass to identify the right PR, triage CI, review, and body blockers, agree on actions with the user, make and commit the fixes, update reviewer threads or PR text, then push once.

2026-06-25
backend-architecture
software-developers

Use when writing, reviewing, or refactoring TypeScript/Node.js backend code, including APIs, middleware, services, repositories, database packages, SDKs, workers, integrations, config DSLs, tests, and backend architecture decisions.

2026-06-02
frontend-architecture
software-developers

Use when writing, reviewing, or refactoring TypeScript frontend code, including React components, Astro or Next.js apps, shared UI packages, client state, server-state fetching, forms, styling systems, routing, analytics, frontend tests, and frontend architecture decisions.

2026-06-02