skills.rest
liangmiQwQ
liangmiQwQCOMMUNITY
Explore all skills by this author →
Website𝕏@liangmiQwQGitHub

finding-on-github

Research git history, issues, and PRs before implementing code changes.

Updated Apr 12, 2026
Search Tags:#git#research#github#code-review#issue-tracking#pull-requests#prevent-waste
One-click install
npx skills add https://github.com/liangmiQwQ/skills --skill finding-on-github
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finding-on-github
Source: https://github.com/liangmiQwQ/skills/tree/main/my-skills/finding-on-github
Command: npx skills add https://github.com/liangmiQwQ/skills --skill finding-on-github

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before touching any code, investigate the history and community activity around the issue to prevent meaningless work and duplications.

Core Features & Use Cases

  • Identify whether a bug is intentional, already solved, or in progress by checking commit history, issues, and PRs.
  • Leverage git and gh CLI as your primary tools to trace blame, search for related discussions, and verify ownership before making changes.
  • Use guardrails to stop work when a solution already exists or someone is actively addressing it.

Quick Start

Ask me to review a repository's history with git blame, issues, and PR checks before making changes.

Frequently Asked Questions about finding-on-github

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check GitHub issue and PR history before making code changes?▼

Researching GitHub commit history and community activity prevents meaningless work and duplications. By checking git blame, issues, and PRs before touching code, you identify whether a bug is intentional, already solved, or currently in progress.

What is the best way to use git blame to prevent duplicate work?▼

Using git blame to trace code ownership prevents duplicate work by revealing whether a bug is intentional or already solved. It allows you to verify ownership and related discussions before implementing fixes in collaborative projects.

Can I use gh CLI to trace pull requests and issues before fixing a bug?▼

Yes, you can use gh CLI to trace pull requests and issues before fixing a bug. The gh CLI serves as a primary tool to search for related discussions and verify community activity, stopping work when a solution already exists.

Does researching open-source code history require git and gh CLI?▼

Researching open-source code history requires git and gh CLI as the primary tools to trace blame, search related discussions, and check issues. These tools provide the guardrails needed to stop work when a solution already exists.

Why should I check repository history before submitting a pull request?▼

You should check repository history before submitting a pull request to prevent meaningless work and duplications. Investigating community activity ensures no one is actively addressing the issue and verifies that the bug is not intentional.

When should I stop working on an open-source code fix?▼

You should stop working on an open-source code fix when researching code history reveals a solution already exists or someone is actively addressing it. Guardrails stop work to prevent duplicating effort in collaborative projects.

Related Skills

Explore More Software Engineering Skills→
theZMCtheZMC
2

read-github-issue

Read GitHub issue status, metadata, and comments via gh CLI.

Community
Intermediate
avvaleavvale

commit-pr

Commit changes, push to a feature branch, and create a GitHub Pull Request.

Official
Advanced
goderechogoderecho

scartissue

Analyze code branches against historical bug data to flag risky changes.

Official
Intermediate
yanochka11yanochka11

pr-writer

Generate GitHub pull request descriptions from branch changes and git history.

Community
Advanced