implement-plan-phase-github SKILL.md skillA
implement-plan-phase-github from codelytv/agent-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add codelytv/agent-harness/implement-plan-phase-github@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- codelytv/agent-harness
- Path
.agents/skills/implement-plan-phase-github/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0, committed Nov 17, 2026
- Size
- 6,074 bytes
- Repository stars
- 319
- License
- none declared
Implement one phase of a plan stored as GitHub issues in the repository of the current working directory. Given the URL of a phase (child) issue it implements that phase; given the parent plan issue it finds and implements the current phase. Only implements a single phase per invocation, then stops for user review. It opens a pull request that references the phase issue so merging it closes the issue automatically. Never merges the pull request.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 🫡 Implement a plan phase > [!CRITICAL] > Implement **ONLY ONE phase** per invocation. After completing the current phase, **STOP** and wait for the user to review the changes. Never proceed to the next phase without explicit user approval. > [!CRITICAL] > **Never merge the pull request.** This skill may create a feature branch, commit, push and open a pull request, but the user decides when to merge. Merging is what closes the phase issue. ## 🎯 Input This skill is invoked as `/implement-plan-phase-github <github-issue-url>`. The URL can point to either: - A **phase (child) issue**: implement that phase. - The **parent plan issue**: find the current phase and implement it (see below). If no URL is provided, ask the user for it before doing anything else. ## 🗂️ Repository The plan and its phases live as GitHub issues in the repository of the current working directory, and the pull requests are opened there too. Never hardcode a repository: let `gh` resolve it from the local Git remote. ```bash gh issue view <number> gh issue develop <number> --checkout gh pr create --title "..." --body "..." ``` …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2mfr6h35z7h3r5r3/b243194ff0d8ec8f57bd0b6aa942b9afb05346b38b47b43ad2e05453e1aae924.json
Then /plugin install implement-plan-phase-github@markdownregistry-2mfr6h35z7h3r5r3 in Claude Code. It installs v1.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add codelytv/agent-harness/implement-plan-phase-github@sha256:b243194ff0d8ec8fThe line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2mfr6h35z7h3r5r3)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in codelytv/agent-harness/implement-plan-phase-github since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of implement-plan-phase-github from somewhere else? Ask it: where did my implement-plan-phase-github come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 17, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/implement-plan-phase-github/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6074 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
codelytv/agent-harness · 319 stars · license none declared · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2mfr6h35z7h3r5r3 GET https://markdownregistry.com/api/v1/resolve?ref=codelytv/agent-harness/implement-plan-phase-github GET https://markdownregistry.com/api/v1/blob/b243194ff0d8ec8f57bd0b6aa942b9afb05346b38b47b43ad2e05453e1aae924
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from codelytv/agent-harness
Every file in codelytv/agent-harness
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.