Menu
Add a new default pattern to defaults/patronum.json with correct schema and validation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Adopt portless for stable, git-worktree-aware .localhost dev URLs following its documented best practices (pinned devDependency + portless.json + dev/dev:app script split — never a hand-rolled slug or sh -c wrapper), then wire it into Conductor via .conductor/settings.toml. Detects the stack first, wraps ONLY the JS/TS frontend dev server, and researches per-workspace isolation for backends/DB/Docker that portless can't cover. Use when asked to set up portless, fix stable dev URLs across worktrees, or make a repo Conductor-friendly for parallel agents.
Create or update GitHub issues for bug reports, feature requests, and refactor tasks using the gh CLI. Use when the user wants to file a ticket, create an issue, report a bug, request a feature, plan a refactor, or update an existing GitHub issue. Also triggers for new issue, open a ticket, file a bug, feature request, create task, or mentions wanting to track work in GitHub Issues.
Sets up, audits, or migrates release-please (Conventional-Commit versioning, changelogs, GitHub releases). Use to set up release automation, automated versioning/changelogs, or release-please; to audit, review, fix, or question an existing setup; or to switch release forms (single ↔ per-module) without breaking changelog/tag history.
Sets up a repo for Conductor end-to-end: install/setup script (automatic), selectable Run targets (with more than one, no default so nothing autostarts), and archive cleanup (automatic) — writes .conductor/settings.toml. Use when asked to set up conductor, configure a workspace, add run targets, stop conductor autostarting, make a run-button menu, or add archive/cleanup on workspace removal.
Release & supply-chain readiness audit: gathers evidence from real workflows, manifests, and repo settings, compares against a gold-standard reference stack, has an adversarial subagent try to refute the draft, and returns a prioritized action plan (P1–P3) whose fixes are delegated to the sibling setup skills. Use when asked to audit release automation, publishing security, CI or supply-chain maturity, or whether a repo is ready to release. For a whole-repo health check (docs, tests, code quality) use maturity-analysis instead.
Audits and sets up .github/dependabot.yml: recommends a grouping mode (low-noise, balanced, fine-grained) from the repo's use-case, gates setup on pinned dependency versions, wires CODEOWNERS over the deprecated reviewers key, groups security updates. Use when asked to set up, review, fix, or audit Dependabot / automated dependency updates / dependency grouping.
| name | patronum-dev-add-default-pattern |
| argument-hint | "<pattern>" --reason "<reason>" |
| description | Add a new default pattern to defaults/patronum.json with correct schema and validation. |
| disable-model-invocation | true |
| allowed-tools | Read, Edit, Bash(jq *), Bash(CLAUDE_PLUGIN_ROOT=* bash scripts/patronum-verify.sh) |
Add a new pattern to the default protection list shipped with the plugin.
Read defaults/patronum.json
Edit defaults/patronum.json to add the new entry with the correct schema:
{
"pattern": "<pattern>",
"type": "glob",
"reason": "<reason>",
"addedAt": "<current ISO timestamp>",
"source": "default"
}
jq empty defaults/patronum.json
Copy the updated defaults to the config and run verify:
cp defaults/patronum.json ~/.claude/patronum.json
CLAUDE_PLUGIN_ROOT="$(pwd)" bash scripts/patronum-verify.sh
Confirm the pattern was added and tests pass.