How do I install the Dep Update skill?

Run npx skillmds@latest add ai-dynamo-dynamo/dep-update in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dep Update safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dep Update?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dep Update free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Dep Update?

ai-dynamo (@ai-dynamo-dynamo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dep Update by ai-dynamo-dynamo — Agent Skill

Name: Dep Update
Rating: 4.5 (4 reviews)
Author: ai-dynamo

Dep Update

Updates Dynamo Enhancement Proposal lifecycle state in GitHub, including triage, PIC assignment, review, approval, and status label changes. Use when triaging a new DEP, assigning a PIC, or moving a proposal through review and approval.

ai-dynamo Updated Sep 10, 2026

File contents

Skill: Update DEP Lifecycle

Purpose

Update DEP status through its lifecycle — triage, review, approve, defer, or close. Covers the PIC workflow from initial assignment through final approval.

When to Use

When triaging DEP issues, reviewing a DEP as PIC or reviewer, approving a DEP that is under review, or updating DEP status.

Workflow

Triage (assign PIC)

List unassigned DEPs:

gh issue list --repo ai-dynamo/dynamo \
  --label "dep:draft" \
  --json number,title,labels,assignees \
  --jq '.[] | select(.assignees | length == 0)'

Assign PIC based on the area label:

gh issue edit <number> --repo ai-dynamo/dynamo \
  --add-assignee "<github-username>"

Move to review when the spec is ready:

gh issue edit <number> --repo ai-dynamo/dynamo \
  --remove-label "dep:draft" \
  --add-label "dep:under-review"

Review

Read the DEP issue and discussion:

gh issue view <number> --repo ai-dynamo/dynamo
gh issue view <number> --repo ai-dynamo/dynamo --comments

Post review feedback as comments on the issue.
Request changes or clarifications from the author.

Approve

Verify the issue is under review:

gh issue view <number> --repo ai-dynamo/dynamo --json labels

Post the approval comment:

gh issue comment <number> --repo ai-dynamo/dynamo --body "/approve"

If this is the PIC approving (or all required reviewers have approved), update the label:

gh issue edit <number> --repo ai-dynamo/dynamo \
  --remove-label "dep:under-review" \
  --add-label "dep:approved"

Notes

For straightforward DEPs, the PIC's /approve is sufficient.
For multi-reviewer DEPs, the PIC maintains a pinned approval checklist and updates the label only when all required approvals are collected.
/approve comments are searchable for audit: gh search issues --repo ai-dynamo/dynamo "/approve" in:comments
Area labels are bare names (e.g., frontend, router) — no prefix.

---name: dep-updatedescription: Updates Dynamo Enhancement Proposal lifecycle state in GitHub, including triage, PIC assignment, review, approval, and status label changes. Use when triaging a new DEP, assigning a PIC, or moving a proposal through review and approval.license: Apache-2.0---# Skill: Update DEP Lifecycle## PurposeUpdate DEP status through its lifecycle — triage, review, approve,defer, or close. Covers the PIC workflow from initial assignmentthrough final approval.## When to UseWhen triaging DEP issues, reviewing a DEP as PIC or reviewer,approving a DEP that is under review, or updating DEP status.## Workflow### Triage (assign PIC)1. **List unassigned DEPs**:```bashgh issue list --repo ai-dynamo/dynamo \ --label "dep:draft" \ --json number,title,labels,assignees \ --jq '.[] | select(.assignees | length == 0)'```2. **Assign PIC** based on the area label:```bashgh issue edit <number> --repo ai-dynamo/dynamo \ --add-assignee "<github-username>"```3. **Move to review** when the spec is ready:```bashgh issue edit <number> --repo ai-dynamo/dynamo \ --remove-label "dep:draft" \ --add-label "dep:under-review"```### Review1. **Read the DEP issue and discussion**:```bashgh issue view <number> --repo ai-dynamo/dynamogh issue view <number> --repo ai-dynamo/dynamo --comments```2. **Post review feedback** as comments on the issue.3. **Request changes** or clarifications from the author.### Approve1. **Verify the issue is under review**:```bashgh issue view <number> --repo ai-dynamo/dynamo --json labels```2. **Post the approval comment**:```bashgh issue comment <number> --repo ai-dynamo/dynamo --body "/approve"```3. **If this is the PIC approving** (or all required reviewers have approved), update the label:```bashgh issue edit <number> --repo ai-dynamo/dynamo \ --remove-label "dep:under-review" \ --add-label "dep:approved"```## Notes- For straightforward DEPs, the PIC's `/approve` is sufficient.- For multi-reviewer DEPs, the PIC maintains a pinned approval checklist and updates the label only when all required approvals are collected.- `/approve` comments are searchable for audit: `gh search issues --repo ai-dynamo/dynamo "/approve" in:comments`- Area labels are bare names (e.g., `frontend`, `router`) — no prefix.

Frequently asked questions