rakovi4/prompt-update
.claude/skills/prompt-update/SKILL.md
Classify new content (rule, pattern, workflow step) and write it to the correct documentation layer. Use when user wants to add prompt documentation or mentions /prompt-update command.
$ install --global
skillsauthnpx skillsauth add rakovi4/continue-example prompt-updateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 1:49 AM5.8s1 file scanned
SKILL.md
- name:
- prompt-update
- description:
- Classify new content (rule, pattern, workflow step) and write it to the correct documentation layer. Use when user wants to add prompt documentation or mentions /prompt-update command.
/prompt-update - Classify & Place Documentation Content
Classify a piece of new content and write it to the correct file(s) in the project's documentation layers.
Usage
/prompt-update "always use eq() not any() in Mockito"
/prompt-update "test-review should catch Fake storage assertions"
/prompt-update # Interactive — asks what to add
Workflow
- Parse input. If no content provided, ask the user what to add.
- Understand the content. What does it mean? Is it a principle, a detection pattern, a code example, a workflow step?
- Classify targets using
.claude/templates/documentation/prompt-update-classification.md. Walk ALL 4 decision questions explicitly — principle, detection pattern, code example, layer-specific context. Show the classification before writing:
Most updates touch 2+ files. If only one target is identified, double-check — a rule without detection won't be enforced, a detection without a template won't guide the fix.1. Principle? → frontend-rules.md (new section) 2. Detection? → refactor-agent.md (smell table) + scan-checklist.md (A-check) 3. Template? → new templates/refactoring/extract-tailwind-class.md 4. Layer-specific? → n/a - Check for duplication — grep key terms across
.claude/rules/,.claude/tech/,.claude/agents/,.claude/skills/,.claude/templates/. If a duplicate exists, report it and ask: skip, merge, or replace? - Write to all target files in one pass. Match each file's existing style.
- Tech-agnostic gate — for every write targeting a universal file (
.claude/rules/,.claude/templates/), scan the content you just wrote for tech leaks. See "Tech-Agnostic Verification" in the classification template. If a leak is found, rephrase in universal terms first — only relocate to tech binding when the content is inherently tech-specific. - Report what was written and where (see Output format in classification template).
- Verify with
/skill-creator— see Impact Assessment in classification template.
Constraints
- Never create new rules files — content fits existing files
- Never place fenced code blocks in agents or skills — extract to templates
- Never edit skill files directly — delegate to
/skill-creator - Always check for duplication before writing
- Preserve existing formatting and section structure of target files
- When the principle already exists in a higher layer, don't re-state it — add only the enforcement mechanism
Templates
.claude/templates/documentation/prompt-update-classification.md— classification guide, decision process, examples, impact assessment
Next Steps
/prompt-refactor {target-file}— verify the file is still structurally clean./skill-creator— verify affected skills respect the new content (when Impact Assessment says to run it).
Related Skills
rakovi4/test-usecase
testing
VerifiedTrustedCommunity
Run use-case module tests quickly. Use when user wants to run use-case tests or mentions /test-usecase command.
2SKILL.mdUpdated Apr 16, 2026
rakovi4/test-spec
development
VerifiedTrustedCommunity
Generate BDD test specifications for story in 6 categories (API, UI, Load, Infrastructure, Security, Integration). Use when user wants to create test cases or mentions /test-spec command.
2SKILL.mdUpdated Apr 16, 2026
rakovi4/test-review
testing
VerifiedTrustedCommunity
Review tests to replace loose validation (contains, isNotNull, isNotEmpty) with strict validation (isEqualTo on parsed fields). Use when user wants to improve test assertions or mentions /test-review command.
2SKILL.mdUpdated Apr 16, 2026
rakovi4/test-frontend
development
VerifiedTrustedCommunity
Run frontend tests. Use when user wants to run frontend unit tests or mentions /test-frontend command.
2SKILL.mdUpdated Apr 16, 2026