org-map

Answer organization-level questions from the org's own map - every repo, account and provider, the rules that hold across them, and the command that shows each one's live state - and build that map when it does not exist yet. Use for "what runs where", "who applies the infrastructure", "where is this tracked", "what is open across the org", and before you plan work that spans repos or accounts.

Jump to install Review files

Repository: Dev-of-Codes-LLC/agent-toolkit
Last source activity: October 24, 2026 at 23:05
Detected SKILL.md language: English
Stars: 0
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/Dev-of-Codes-LLC/agent-toolkit/tree/main/plugins/devofcodes-repo-ops/skills/org-map.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/Dev-of-Codes-LLC/agent-toolkit --skill org-map

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

3 files

SKILL.md

Source instructions · Read-only preview

name	org-map
description	Answer organization-level questions from the org's own map - every repo, account and provider, the rules that hold across them, and the command that shows each one's live state - and build that map when it does not exist yet. Use for "what runs where", "who applies the infrastructure", "where is this tracked", "what is open across the org", and before you plan work that spans repos or accounts.

Back to search Back to installation

docker-cleanup

Audit and reclaim a local Docker Desktop environment safely, tier by tier (build cache, broken builders, orphan networks, exited containers, leftover images, and finally volumes only by explicit name). Use this whenever the user mentions Docker disk usage, "docker is eating my disk", prune, dangling or leftover images, old compose projects, stale volumes, build cache size, or asks what Docker resources exist and which are safe to remove, even if they only say "clean up docker" or "why is my C drive full". Also use it after a burst of throwaway compose projects (isolated test or smoke stacks) to clear what they left behind.

2026-11-12

feature-doc

Turn a finished feature, unit, epic, or pull request into one polished, wiki-ready product feature document, as Markdown in the repository (the source of record) plus a self-contained HTML reference sheet (lettered panels, a title block, optional whiteboard-style diagram) for sharing. Use this whenever the user wants a feature write-up, a wiki page, a "feature doc", a product page, a reference sheet, a release or unit summary that others can read, a presentable version of a final report, a page to share with a friend, customer, or stakeholder about something that was built, or asks to "document what we built" or "make this presentable", even if they only say "write it up" after finishing a piece of work.

2026-10-24

land-branch

Land a feature branch on a main that moved ahead: assess the divergence, rebase, open or update the PR, wait for every check to pass, squash-merge, then run the project's own rebuild step if it has one. Covers failing checks, stuck checks, merge refusals and a failed rebuild. Use when asked to land, merge or ship a branch, especially after another session merged work first.

2026-10-24

View all from this repository

org-map

Source facts

Install options

Install with an AI assistant

Review the source files

More from this repository

Install with an AI assistant

More from this repository