Menu
Archive completed change proposals from docs/changes/ to docs/_archive/ after verifying preconditions.
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
Feature development workflow. Propose a change, plan implementation, execute with gates, and verify.
Analyze DTVM's dMIR intermediate representation and compilation pipeline. Translates EVM bytecode sequences into dMIR pseudocode, then into x86 pseudocode, and evaluates performance cost at each stage. Use when the user asks about dMIR instructions, EVM-to-dMIR conversion, dMIR-to-x86 lowering, JIT compilation cost analysis, EVM opcode performance evaluation, or EVM->dMIR performance optimization.
Profile DTVM execution using Linux perf and generate categorized analysis reports. Use when the user wants to profile a DTVM command, find performance hotspots, break down JIT-compiled EVM basic block execution time, analyze host function overhead, or mentions "perf", "profile", "hotspot", "breakdown", or "bottleneck" in the context of DTVM execution. The user provides a dtvm command line (including bytecode path, calldata, execution mode, etc.).
| name | archive |
| description | Archive completed change proposals from docs/changes/ to docs/_archive/ after verifying preconditions. |
Archive completed change proposals from docs/changes/ to docs/_archive/<YYYY-MM>/.
dev-workflow skillAll of the following must be true before archiving:
| # | Condition | How to Verify |
|---|---|---|
| 1 | Implementation complete | All checklist items in the change doc are done |
| 2 | Build and tests pass | Run the project's build and test commands |
| 3 | Code review approved | PR has been approved |
| 4 | Branch merged | Feature branch merged into target branch |
| 5 | Module specs updated | Related specs in docs/modules/ reflect any contract changes |
If conditions are not met, report what is missing and suggest completing those first.
If the user specifies a change, locate it. Otherwise, list changes in docs/changes/ with status Implemented for the user to choose.
Check each precondition:
git branch --merged)Present a summary:
Archive check: YYYY-MM-DD-<slug>
Tasks: N/N complete
Branch: merged into main
Module specs: updated / needs sync
Tests/review: user confirmation required
Proceed?
After confirmation:
docs/_archive/<YYYY-MM>/ if it does not existdocs/changes/YYYY-MM-DD-<slug>/ to docs/_archive/<YYYY-MM>/<slug>/docs/_archive/README.mdBranch and worktree cleanup are out of scope for this skill โ leave them to the user.
If multiple changes are ready, list them all and let the user select which to archive.