lov-gh-contribute SKILL.md skillA
lov-gh-contribute from lovstudio/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lovstudio/skills/lov-gh-contribute@v0.2.1Pins v0.2.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lovstudio/skills
- Path
skills/gh-contribute/SKILL.md- Versions recorded
- 6
- Latest version
- v0.2.1, committed Sep 25, 2026
- First version recorded
- Aug 10, 2026
- Size
- 8,590 bytes
- Repository stars
- 72
- License
- MIT
Contribute a clean, professional pull request to someone else's GitHub repository: fork → clone → branch → commit → push → open PR, with smart splitting into one or multiple PRs based on the scope of changes. Trigger when the user says "给这个 repo 提 PR"、"贡献代码"、"fork 然后改再 PR"、 "contribute to this repo", "open a PR to upstream", "submit a PR to <owner>/<repo>".
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
# 开源贡献助手 · Open Source Contributor Turn local changes into a clean, professional pull request against an upstream repo you don't own. Handles the full fork → branch → commit → push → PR pipeline, and splits work into multiple PRs when the changes span unrelated concerns. ## When to Use - User wants to contribute to an open-source project they don't have write access to - User already has local edits and needs them shipped as a PR upstream - User asks to "fork this repo and send a PR" - User has mixed changes (e.g. docs + feature + refactor) and wants them split properly ## Non-Goals - Does **not** write code changes — assumes the user (or a prior step) already has the desired modifications in the working tree or in their head - Does **not** review the project's own PRs (see `gh-tidy`) - Does **not** mirror to GitLab/Gitea — GitHub only ## Workflow (MANDATORY) Execute steps in order. Do not skip confirmations. ### Step 1: Identify the target repo Determine the upstream `owner/repo`: 1. If the user pasted a URL or `owner/repo` string → use it 2. Otherwise run `git remote -v` in the current directory and pick the `origin` …
Read the whole file at its exact version.
How to install
mdr add lovstudio/skills/lov-gh-contribute@sha256:fa36eb4809f9f623The line at the top of this page pins the label v0.2.1, 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_gavmzsqsab3c3ww5)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 10, 2026 and Sep 25, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.2.1 latest | 2026-09-25 | 4b67fd1 | 8,590 B | A | view · diff |
| v0.2.0 | 2026-09-07 | a09848e | 8,590 B | A | view · diff |
| v0.2.0 | 2026-08-23 | 00fafa8 | 8,590 B | A | view · diff |
| v0.1.2 | 2026-08-10 | d704a55 | 7,868 B | A | view · diff |
| v0.1.2 | 2026-08-10 | 22e49cf | 7,241 B | A | view · diff |
| v0.1.2 | 2026-08-10 | 08d33b8 | 7,241 B | A | view |
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 (8590 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
lovstudio/skills · 72 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gavmzsqsab3c3ww5 GET https://markdownregistry.com/api/v1/resolve?ref=lovstudio/skills/lov-gh-contribute GET https://markdownregistry.com/api/v1/blob/fa36eb4809f9f623d8decd03d4ff6891289b8d1c59a2081b25bd8f2212ae501f
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.