القائمة
Suggest protection patterns based on project context. Invoke automatically when user mentions a new tech stack, cloud provider, or sensitive tooling. Also invoke when user asks what to protect.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
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.
استنادا إلى تصنيف SOC المهني
| name | patronum-suggest |
| description | Suggest protection patterns based on project context. Invoke automatically when user mentions a new tech stack, cloud provider, or sensitive tooling. Also invoke when user asks what to protect. |
| allowed-tools | Bash(bash "${CLAUDE_PLUGIN_ROOT}/scripts/patronum-list.sh"), Bash(bash "${CLAUDE_PLUGIN_ROOT}/scripts/patronum-add.sh" *), Glob, Read, AskUserQuestion, WebSearch |
Analyze the current project and suggest relevant protection patterns.
Check what tools and cloud services are in use. Look at:
package.json, go.mod, requirements.txt, Gemfile, Cargo.toml.tf files (Terraform), docker-compose.yml, Dockerfile.gcloud/, .azure/, cloud config directories.github/workflows/, .gitlab-ci.yml)Use WebSearch to find known sensitive files, credential paths, and secret locations for the detected technologies. Search for patterns like:
This ensures suggestions cover technology-specific risks beyond the hardcoded list.
Run: bash "${CLAUDE_PLUGIN_ROOT}/scripts/patronum-list.sh" to see what is already protected.
Based on detected stack and web research, suggest patterns that are NOT yet protected. Common suggestions include:
**/*.tfvars, **/*.tfstate, **/.terraform/environment~/.config/gcloud/credentials.db, **/service-account*.json~/.azure/accessTokens.json, ~/.azure/msal_token_cache.json~/.gem/credentials~/.gradle/gradle.properties, ~/.m2/settings.xml**/kubeconfig, **/*.kubeconfig~/.vault-token~/.gnupg/*Also suggest command patterns where the stack warrants it, using the Bash(<command>) prefix-match format (see docs/rules/bash-commands.md), e.g. Bash(aws sts), Bash(gcloud auth print-access-token), Bash(printenv).
This catalogue can go stale — verify each path against the web research from Step 2 before suggesting it (e.g. Azure's accessTokens.json only exists on older CLI versions; modern ones use the MSAL token cache).
Include any additional patterns discovered via web search.
Use AskUserQuestion to present the suggestions as a formatted list with reasons.
Let the user select which patterns to add.
For each confirmed pattern, run:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/patronum-add.sh" "<pattern>" --reason "<reason>"
Present the final updated protection list as a markdown table.