patinaproject-skills

Skills used by the Patina Project team

Installable agent skills for repository scaffolding, project-local skill installation, GitHub workflows, issue branch setup, issue development, PR finishing, Codex PR feedback polling, isolated local code review, and local branch updating. They are available across Claude Code, Codex, and any agent runtime that reads AGENTS.md.

Quickstart

npx skills@latest add patinaproject/skills

The CLI prompts you to pick which skills to install and auto-detects your agent.

Install via the host marketplace (alternative)

Claude Code:

/plugin marketplace add patinaproject/skills
/plugin install patinaproject-skills@patinaproject-skills

Codex:

/marketplace add patinaproject/skills
/install patinaproject-skills

Security note: For environments where you want to prevent install scripts from running during CLI execution, prefix the npx command above with npm_config_ignore_scripts=true. Not required for standard use.

Related skills

For skill discovery and catalog navigation, install find-skills from the vercel-labs/skills catalog:

npx skills@latest add vercel-labs/skills@find-skills

Why these skills exist

using-github

GitHub work - filing issues, editing issues, starting branches, writing changelogs, preparing PRs - is repetitive and convention-sensitive. Without a shared skill, every agent session re-derives the same rules from scratch and produces inconsistent output. using-github reads repository rules and routes to the correct workflow for each task.

See ./skills/using-github/ for the full README and skill contract.

install-skills

Shared workflow skills should be added to a repository without mutating an operator's global agent environment. install-skills gives agents a canonical npx skills@latest workflow: read local guidance, inspect skills-lock.json, install selected skills project-locally for all supported agent targets, and verify the resulting lockfile and overlay changes.

See ./skills/install-skills/ for the skill contract.

new-branch

Issue-linked implementation should start from the repository default branch on a predictable local branch. new-branch resolves an issue, derives GitHub's default issue-branch name, refuses dirty worktrees, and creates or switches to the local branch without pushing, installing dependencies, committing, or creating a PR.

See ./skills/new-branch/ for the skill contract.

develop-issue

End-to-end issue work needs a single entrypoint without weakening the focused skills that already own branch setup, test-driven implementation, diagnosis, local review, and PR finishing. develop-issue takes exactly one same-repo issue reference, coordinates new-branch, tdd, diagnose, review-code, and finish-pr, and stops for human-owned ambiguity instead of inventing scope.

See ./skills/develop-issue/ for the skill contract.

review-code

Local issue work needs a fresh review pass before publishing. review-code computes the default-branch merge-base, includes committed, staged, unstaged, and untracked changes, then dispatches a fresh read-only reviewer to report findings without editing files or mutating GitHub state.

See ./skills/review-code/ for the skill contract.

finish-pr

Finishing branch work is more than opening a pull request. finish-pr verifies the local diff, commits with the repository convention, pushes when needed, creates or updates a ready-for-review PR from the template, watches checks, and stops at ready-to-merge.

See ./skills/finish-pr/ for the skill contract.

codex-pr-feedback-loop

PR review follow-up should preserve the Codex app chat context after the first successful push. codex-pr-feedback-loop creates a thread automation that polls the current PR, handles actionable review feedback and objective low-risk cleanup, pushes verified fixes, replies with evidence, and stops when no actionable work remains.

See ./skills/codex-pr-feedback-loop/ for the skill contract.

update-branch

Keeping a work branch current should be a local git operation unless an operator chooses to publish it. update-branch fetches the selected base branch, defaults to origin/HEAD, guards dirty work, merges with git merge --no-ff, and reports the local-only result plus the push command to run later.

See ./skills/update-branch/ for the skill contract.

scaffold-repository

Teams spend disproportionate time on repo plumbing - commit conventions, markdown linting, PR templates, and Husky hooks. scaffold-repository emits the full Patina Project baseline and keeps it aligned on rerun.