How do I install the Finding On Github skill?

Run npx skillmds@latest add liangmiqwq/finding-on-github 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 Finding On Github safe to use?

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

Which AI agents work with Finding On Github?

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 Finding On Github free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Finding On Github?

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

Finding On Github by liangmiqwq — Agent Skill

Name: Finding On Github
Author: liangmiqwq

Finding On Github

If you are now working with with a opensource project while I'm not a maintainer or author Load this skill when I ask things like `is there a bug?` and when you sense I am willing to contribute to it, or when I am confirming whether there is a problem. Load this skill when you are modifying an existing feature without a certain reason

liangmiqwq a41e290 1.9 KB Updated Sep 17, 2026

File contents

Finding on GitHub

Your job is to prevent meaningless work for both the user and agents. Before touching any code, investigate the history and community activity around the issue. Feel free to stop me if the work is already done or in progress.

Use git and gh CLI as your primary tools.

Step 1 — Check if the behavior is intentional

Use git blame to find who last changed the relevant code, then trace the commit:

git blame <file> -L <line>,<line>
git show <commit-hash>

Search for related commits and PRs linked to that change:

gh search commits "<keyword>" --repo <owner>/<repo>

Goal: Determine whether this is a known intentional decision or an actual bug.

Step 2 — Search existing Issues

Search for anyone who has already reported the same problem or requested the same feature:

gh issue list --repo <owner>/<repo> --search "<keyword>" --state all

Read through the top matches. If you find a relevant issue:

Summarize what was discussed
Note the current status (open, closed, won't fix, etc.)
If someone is actively working on a fix — stop me and report it

Step 3 — Search existing Pull Requests

Check if a fix or implementation is already in progress:

gh pr list --repo <owner>/<repo> --search "<keyword>" --state all

If an open PR addresses the same problem — stop me and link it. There is no point duplicating effort.

If you loaded this skill and did this inspect, leave a simple line in your response to make sure I can work on it.

---name: finding-on-githubdescription: If you are now working with with a opensource project while I'm not a maintainer or author Load this skill when I ask things like `is there a bug?` and when you sense I am willing to contribute to it, or when I am confirming whether there is a problem. Load this skill when you are modifying an existing feature without a certain reason---# Finding on GitHubYour job is to **prevent meaningless work** for both the user and agents. Before touching any code, investigate the history and community activity around the issue. Feel free to stop me if the work is already done or in progress.Use `git` and `gh` CLI as your primary tools.---## Step 1 — Check if the behavior is intentionalUse `git blame` to find who last changed the relevant code, then trace the commit:```bashgit blame <file> -L <line>,<line>git show <commit-hash>```Search for related commits and PRs linked to that change:```bashgh search commits "<keyword>" --repo <owner>/<repo>```**Goal:** Determine whether this is a known intentional decision or an actual bug.---## Step 2 — Search existing IssuesSearch for anyone who has already reported the same problem or requested the same feature:```bashgh issue list --repo <owner>/<repo> --search "<keyword>" --state all```Read through the top matches. If you find a relevant issue:- Summarize what was discussed- Note the current status (open, closed, won't fix, etc.)- **If someone is actively working on a fix — stop me and report it**---## Step 3 — Search existing Pull RequestsCheck if a fix or implementation is already in progress:```bashgh pr list --repo <owner>/<repo> --search "<keyword>" --state all```If an open PR addresses the same problem — **stop me and link it**. There is no point duplicating effort.If you loaded this skill and did this inspect, leave a simple line in your response to make sure I can work on it.

Frequently asked questions