PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Start implementation for a GitHub issue. An agent skill from NTCoding/living-architecture.
Apache-2.0Auto-check passed
Install Dev Workflow Start Implementation
$ npx skills add NTCoding/living-architecture --skill dev-workflow-start-implementation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NTCoding/living-architecture dev-workflow-start-implementation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NTCoding/living-architecture.git skills-src && mkdir -p .claude/skills && cp -r skills-src/tools/dev-workflow-v2/skills/dev-workflow-start-implementation .claude/skills/dev-workflow-start-implementation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "dev-workflow-start-implementation" agent skill from https://github.com/NTCoding/living-architecture/tree/main/tools/dev-workflow-v2/skills/dev-workflow-start-implementation into .claude/skills/dev-workflow-start-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-workflow-start-implementation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NTCoding/living-architecture/tree/main/tools/dev-workflow-v2/skills/dev-workflow-start-implementationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NTCoding/living-architecture --skill dev-workflow-start-implementation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NTCoding/living-architecture dev-workflow-start-implementation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NTCoding/living-architecture.git skills-src && mkdir -p .agents/skills && cp -r skills-src/tools/dev-workflow-v2/skills/dev-workflow-start-implementation .agents/skills/dev-workflow-start-implementation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dev-workflow-start-implementation" agent skill from https://github.com/NTCoding/living-architecture/tree/main/tools/dev-workflow-v2/skills/dev-workflow-start-implementation into .agents/skills/dev-workflow-start-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-workflow-start-implementation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NTCoding/living-architecture --skill dev-workflow-start-implementation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NTCoding/living-architecture dev-workflow-start-implementation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NTCoding/living-architecture.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/tools/dev-workflow-v2/skills/dev-workflow-start-implementation .cursor/skills/dev-workflow-start-implementation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dev-workflow-start-implementation" agent skill from https://github.com/NTCoding/living-architecture/tree/main/tools/dev-workflow-v2/skills/dev-workflow-start-implementation into .cursor/skills/dev-workflow-start-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-workflow-start-implementation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NTCoding/living-architecture.git --path tools/dev-workflow-v2/skills/dev-workflow-start-implementation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NTCoding/living-architecture --skill dev-workflow-start-implementation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NTCoding/living-architecture dev-workflow-start-implementation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NTCoding/living-architecture.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/tools/dev-workflow-v2/skills/dev-workflow-start-implementation .gemini/skills/dev-workflow-start-implementation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dev-workflow-start-implementation" agent skill from https://github.com/NTCoding/living-architecture/tree/main/tools/dev-workflow-v2/skills/dev-workflow-start-implementation into .gemini/skills/dev-workflow-start-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-workflow-start-implementation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NTCoding/living-architecture dev-workflow-start-implementationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NTCoding/living-architecture --skill dev-workflow-start-implementation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NTCoding/living-architecture.git skills-src && mkdir -p .github/skills && cp -r skills-src/tools/dev-workflow-v2/skills/dev-workflow-start-implementation .github/skills/dev-workflow-start-implementation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dev-workflow-start-implementation" agent skill from https://github.com/NTCoding/living-architecture/tree/main/tools/dev-workflow-v2/skills/dev-workflow-start-implementation into .github/skills/dev-workflow-start-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-workflow-start-implementation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NTCoding/living-architecture --skill dev-workflow-start-implementation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NTCoding/living-architecture dev-workflow-start-implementation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NTCoding/living-architecture.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/tools/dev-workflow-v2/skills/dev-workflow-start-implementation .opencode/skills/dev-workflow-start-implementation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dev-workflow-start-implementation" agent skill from https://github.com/NTCoding/living-architecture/tree/main/tools/dev-workflow-v2/skills/dev-workflow-start-implementation into .opencode/skills/dev-workflow-start-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-workflow-start-implementation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
dev-workflow-start-implementation- GitHub stars
- 139
- Token cost
- ~193 tokens
- SKILL.md length
- 46 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Start implementation for a GitHub issue. An agent skill from NTCoding/living-architecture.
- Explicitly invokes $dev-workflow-start-implementation with an issue number
- Calls pnpm and git
What it does
Dev Workflow Start Implementation is an agent skill from NTCoding/living-architecture. Start implementation for a GitHub issue. Use only when the user explicitly invokes $dev-workflow-start-implementation with an issue number.
Its SKILL.md is about 190 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with GitHub. The repository describes itself as: Extra software architecture from your code as living documentation. AI-assisted. The licence is Apache-2.0.
When your agent uses it
- Explicitly invokes $dev-workflow-start-implementation with an issue number
Example prompts
- “/dev-workflow-start-implementation”
What it can do on your machine
Read from SKILL.md and the folder at commit a24bc9f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpmgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Dev Workflow Start Implementation loads about 193 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 46 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from NTCoding/living-architecture at commit a24bc9f, republished under its Apache-2.0 licence (© NTCoding). 46 words, ~193 tokens.
Download SKILL.mdSave it as
.claude/skills/dev-workflow-start-implementation/SKILL.md (or your agent's skills folder).- name
- dev-workflow-start-implementation
- description
- Start implementation for a GitHub issue. Use only when the user explicitly invokes $dev-workflow-start-implementation with an issue number.
Start Implementation
Use the supplied issue number. Follow the canonical procedure in the plugin's commands/start-implementation.md exactly, with this Codex-specific replacement for its two Claude workflow commands:
pnpm --dir "$(git rev-parse --show-toplevel)/tools/dev-workflow-v2" run codex-workflow init
pnpm --dir "$(git rev-parse --show-toplevel)/tools/dev-workflow-v2" run codex-workflow record-issue <issue-number>The shared command reads Codex's CODEX_THREAD_ID. Do not read a session ID from hook output or substitute any other value.
© NTCoding, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in tools/dev-workflow-v2/skills/dev-workflow-start-implementation of NTCoding/living-architecture.
Open the folder on GitHubat commit a24bc9f
Compare with similar skills
Dev Workflow Start Implementation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dev Workflow Start Implementation this skillNTCoding/living-architecture | 139 | — | ~193 | Automated safety check: Pass | Apache-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Superpowers Sessionsobra/superpowers | 296k | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 83k | 5 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Update V8 Versionopeninterpreter/openinterpreter | 69k | 2 repos | ~845 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Update V8 Version
openinterpreter/openinterpreter
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
More from NTCoding/living-architecture
Ddd
NTCoding/living-architecture
Explore and evaluate domain models collaboratively before implementation.
List Review Threads
NTCoding/living-architecture
List unresolved review threads for the pull request recorded in workflow state.
Workflow
NTCoding/living-architecture
Execute a low-level dev-workflow-v2 state operation. An agent skill from NTCoding/living-architecture.
Related
Works with
Questions about Dev Workflow Start Implementation
What does Dev Workflow Start Implementation do?
Start implementation for a GitHub issue. An agent skill from NTCoding/living-architecture. Dev Workflow Start Implementation is an agent skill from NTCoding/living-architecture. Start implementation for a GitHub issue.
When should I use Dev Workflow Start Implementation?
Dev Workflow Start Implementation fits situations like: explicitly invokes $dev-workflow-start-implementation with an issue number.
How do I install Dev Workflow Start Implementation in Claude Code?
Run `npx skills add NTCoding/living-architecture --skill dev-workflow-start-implementation -a claude-code`. Or copy the skill folder (tools/dev-workflow-v2/skills/dev-workflow-start-implementation in NTCoding/living-architecture) into .claude/skills/dev-workflow-start-implementation in your project. Claude Code loads it when a task matches its description.
How do I install Dev Workflow Start Implementation in Codex?
Run `npx skills add NTCoding/living-architecture --skill dev-workflow-start-implementation -a codex`. Or copy the skill folder (tools/dev-workflow-v2/skills/dev-workflow-start-implementation in NTCoding/living-architecture) into .agents/skills/dev-workflow-start-implementation in your project. Codex loads it when a task matches its description.
Can I use Dev Workflow Start Implementation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NTCoding/living-architecture --skill dev-workflow-start-implementation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dev-workflow-start-implementation, .gemini/skills/dev-workflow-start-implementation, .github/skills/dev-workflow-start-implementation and .opencode/skills/dev-workflow-start-implementation in your project.
What does Dev Workflow Start Implementation need to run?
Going by SKILL.md and its folder, Dev Workflow Start Implementation needs the command-line tools its instructions call (pnpm and git).
Does Dev Workflow Start Implementation access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Dev Workflow Start Implementation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Dev Workflow Start Implementation use?
Dev Workflow Start Implementation is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Dev Workflow Start Implementation use?
About 193 tokens (SKILL.md is roughly 772 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Dev Workflow Start Implementation?
Skills that share tags, products or a category with Dev Workflow Start Implementation: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dev Workflow Start Implementation?
NTCoding (a GitHub user) maintains it in NTCoding/living-architecture, which has 139 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 5, 2026.
Source: NTCoding/living-architecture on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.