القائمة
Apply a hotfix for critical production issues. Use for security vulnerabilities or bugs that prevent core functionality. Triggers on "hotfix", "emergency fix", "critical fix", "production bug".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Operating manual for documentation work in nexus-agents. Use when updating docs, adding new docs, changing doc pipeline, or troubleshooting doc issues. Triggers on "update docs", "add documentation", "doc pipeline".
Periodically exercise ALL nexus-agents feature families end-to-end against a real task — research → synthesize → vote → plan → dev-pipeline → graph workflow → memory → audit — capturing ACTUAL outputs to validate that fixes, docs, and claims hold in real usage (the things unit tests miss: live voter panels, adapter routing, pipeline stage wiring, audit chains). Use after a release, weekly, when several fixes have landed since the last run, or on demand. Triggers on "e2e validation", "end-to-end validation", "dogfood the loops", "validate end to end", "real usage test", "periodic validation run", "full-loop validation".
Run the CI gates locally before pushing, so failures surface in seconds instead of one CI cycle at a time. Enumerates the checks in .github/workflows/, runs the locally-runnable subset in CI's order, and pins the local-vs-CI delta as a memory the first time you work in a repo. Use before `git push` / opening a PR, or when CI just failed on something your local gate missed. Triggers on "pre-push", "before push", "ci parity", "will ci pass", "local gate", "prepush", "pre-push check".
Review code changes following project standards and security guidelines. Checks for lint compliance, type safety, test coverage, and security issues. Use when reviewing PRs, auditing code, checking implementation quality, or running a blind pre-merge review pass before merging your own change. Triggers on "review code", "code review", "check this", "audit", "PR review", "pre-merge review", "blind reviewer", "before merge".
Execute a release following project standards. Use when publishing a new version, creating release tags, or deploying. Triggers on "release", "publish", "version bump", "create release".
Improve an existing technical doc in-place via a phased Audit → Research → Rewrite → Validate workflow. Calls docs-review for audit and validate; never re-derives scoring. Applies answer-first H2s, citation capsules, and info-gain markers per .rules/docs-rubric.md. Use when the user says "rewrite docs", "improve this doc", "optimize doc", "docs rewrite".
| name | hotfix |
| description | Apply a hotfix for critical production issues. Use for security vulnerabilities or bugs that prevent core functionality. Triggers on "hotfix", "emergency fix", "critical fix", "production bug". |
| allowed-tools | Read, Edit, Write, Bash, Grep, Glob, Task |
If criteria not met: Use the bug-fix skill instead.
Create branch from latest release tag:
git tag --sort=-v:refname | head -5 # Find latest tag
git checkout -b hotfix/<issue>-description <latest-tag>
Implement fix with minimal changes — no refactoring, no extras
Fast-track review: Security label + P1 = single-reviewer approval sufficient
Quality gates:
pnpm lint && pnpm typecheck && pnpm test
Merge to main AND cherry-pick to release branch
Immediate release with patch version bump:
# Add changeset for patch bump
pnpm changeset # select patch
git add . && git commit -m "chore: changeset for hotfix"
git push origin main --tags
# CI handles npm publish via OIDC trusted publishing
# Or trigger manually: gh workflow run publish.yml
npm unpublish nexus-agents@<version> # Within 72 hours only
git tag -d v<version> && git push --delete origin v<version>
| Excuse | Counter |
|---|---|
| "Skip tests, it's an emergency" | A hotfix without tests becomes the next regression. Add at least the failing-test-then-fix (Prove-It Pattern). |
| "Bypass the lint gate just this once" | Hotfix bypass is the most expensive shortcut: the next change you ship inherits the broken state. Lint stays. |
| "Skip the PR review, just push" | Hotfix PR review can be quick (one trusted reviewer + admin merge), but the second pair of eyes catches the wrong-fix-for-the-symptom mistake. |
| "Roll forward later, no need for proper rollback plan" | Production users can't wait. Either the hotfix works or there's a rollback plan; "we'll figure it out" is not a plan. |
security-advisory-response instead)pnpm lint && pnpm typecheck && pnpm test pass before merge