miaodi/p4-workflow
skills/p4-workflow/SKILL.md
Use when working with Perforce changelists, shelves, depot state, stream comparisons, file actions, or preparing code for P4 submission.
development
Updated May 21, 2026
$ install --global
skillsauthnpx skillsauth add miaodi/llm_config p4-workflowInstall 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: May 21, 2026, 4:23 AM133.5s1 file scanned
SKILL.md
- name:
- p4-workflow
- description:
- Use when working with Perforce changelists, shelves, depot state, stream comparisons, file actions, or preparing code for P4 submission.
P4 Workflow Skill
Purpose
Work effectively in a Perforce-based codebase with explicit awareness of changelists, shelves, depot state, and review workflow.
When To Use
Use when inspecting pending work, managing changelists, reviewing shelves, comparing revisions, or preparing code for submission in a P4 environment.
Priorities
- Preserve the intended changelist scope.
- Understand depot state before making assumptions about local changes.
- Treat shelves and pending changelists as first-class review units.
- Avoid mixing unrelated work into the same changelist.
- Be explicit about what is local, shelved, pending, or submitted.
Workflow
- Identify the relevant changelist, shelf, stream, and depot path before reviewing or editing.
- Inspect pending files, shelved files, and file actions before reasoning about the change.
- Distinguish local workspace state from depot history and submitted revisions.
- Compare the changelist against the correct base revision or stream.
- Keep edits scoped to the intended changelist and avoid folding unrelated files into it.
- Call out integration, resolve, and branch history concerns when they affect correctness.
- Summarize findings in terms of files, changelist scope, and submission risk.
Changelist Descriptions
When drafting, editing, or reviewing a P4 changelist description, read ../commit-message/SKILL.md and follow the shared Git/P4 commit message template referenced there. A final P4 changelist description must include the actual STARs ID as the final line; ask for the STARs ID if the user did not provide it and it cannot be found in the change context.
Review Checklist
- What changelist or shelf is under review?
- Are the files in the changelist actually related?
- Are there adds, deletes, moves, integrates, or resolves that change the risk profile?
- Is the comparison being made against the correct depot revision or stream?
- Is any relevant context still only shelved and not yet submitted?
- Could workspace state be hiding missing files or stale assumptions?
- Is the changelist too broad to review confidently?
Constraints
- Do not assume Git-style workflows or terminology when the codebase uses Perforce.
- Do not treat a pending changelist as equivalent to submitted history.
- Do not ignore shelves, integrates, or resolves when they affect the meaning of the change.
- Do not mix unrelated fixes into an existing changelist without stating it clearly.
Output
Provide:
- the changelist or shelf being discussed
- the effective scope of the work
- any depot-history or integration concerns
- the review or implementation recommendation
- any follow-up needed before submission
Related Skills
miaodi/computational-learning-notes
development
VerifiedTrustedCommunity
Use when creating C++ learning notes or minimal experiments for low-level computational, numerical, CPU/GPU, compiler, and hardware concepts such as false sharing, floating point, registers, caches, SIMD, atomics, numerical stability, and benchmarking pitfalls.
SKILL.mdUpdated Jun 2, 2026
miaodi/latex-project-build
development
VerifiedTrustedCommunity
Use when configuring, diagnosing, or compiling LaTeX projects, especially multi-file reports, theses, books, chapter-based projects, Overleaf exports, latexmk/arara/Makefile workflows, bibliography/index/glossary passes, or projects that require pdflatex, xelatex, lualatex, latex->dvips, biber, or bibtex.
SKILL.mdUpdated May 28, 2026
miaodi/graph-algorithms
development
VerifiedTrustedCommunity
Use when working with graph traversals (BFS, DFS, level-order), minimum spanning trees, strongly connected components, topological sort, graph coloring, bipartite detection, elimination trees, level-set extraction, parallel graph algorithms, task-tree parallelism, sparse graph representations, and exploiting graph structure for parallel sparse computations.
SKILL.mdUpdated May 21, 2026
miaodi/git-workflow
testing
VerifiedTrustedCommunity
Use when planning or executing Git branch workflows, especially merge/rebase across branches, conflict resolution, safe history rewriting, and recovery from mistakes.
SKILL.mdUpdated May 21, 2026