Loading...
Loading...
Found 13 Skills
Create maintainer-friendly pull requests with clean code and professional communication. Prevents 16 common mistakes that cause PR rejection. Use when: contributing to open source, submitting PRs, or troubleshooting PR rejection, CI failures, or personal artifacts in commits.
Open source contribution best practices. Creating quality pull requests, writing good issues, following project conventions, and collaborating effectively with maintainers.
Use when contributing to the CopilotKit open-source project — forking, cloning, setting up the monorepo, creating branches, running tests, and submitting pull requests against CopilotKit/CopilotKit.
Fork-based PR implementation with isolation check. Runs isolation check before starting work. Triggers: "implement PR", "implement contribution", "fork implementation", "code the PR".
End-to-end open source contribution workflow: from scanning issues to submitting PRs. Use this skill whenever the user wants to contribute to an open source project, find issues to fix, submit a pull request, fork a repo to contribute, fix a GitHub issue, or mentions 'open source contribution'. Also trigger when they provide a GitHub repo URL and ask about contributing, say things like 'help me submit a PR', 'find good first issues', 'I want to contribute to X', or mention fixing bugs in someone else's project.
Plan an open source PR contribution. Takes pr-research output and produces scope, acceptance criteria, and risk assessment. Triggers: "pr plan", "contribution plan", "plan PR", "plan contribution".
Analyze a user-provided Git repository and GitHub issues to confirm contribution rules (CONTRIBUTING, CLA/DCO, templates) and shortlist high-value, maintainer-friendly issues likely to be accepted. Use when a user wants help selecting open-source issues to contribute to, or when triaging a GitHub repo for good first contributions.
Validate feature requests against Genfeed OSS core vs Cloud scope. Helps users and contributors understand whether a feature belongs in the open-source core (submit PR) or Cloud SaaS (subscribe).
Evidence-based resume authenticity audit and report generation skill. This skill should be proactively used when users request resume verification, resume fraud detection, candidate experience investigation, GitHub/open source contribution analysis, identification of role inflation from contributor to maintainer/core author, verification of Sino-foreign cooperative education or school titles, business indicator checks, sorting out public disputes, or production of HTML/PDF reports from investigation results. This skill breaks down resumes, screenshots, links, posts, code repositories, and official records into atomic claims, distinguishes between facts, contradictions, accusations, and unverifiable information, and generates self-contained evidence reports that do not include doxxing information and do not present unsubstantiated accusations as facts.
Upstream codebase exploration for open source contribution. Outputs contribution guidelines, PR patterns, and maintainer expectations. Triggers: "pr research", "upstream research", "contribution research", "explore upstream repo".
Set up a Superset open-source contribution — fork and clone superset-sh/superset, run local dev setup, and follow the repo's contribution rules through to a merge-ready PR. Use when the user wants to contribute to Superset, fix a Superset bug themselves, or prepare a PR against superset-sh/superset.
Implement a chosen contribution in a fork of an open-source project: verify the user's fork already exists (stop and ask the user to fork if it does not), strictly follow the upstream repository's conventions (CONTRIBUTING.md, AGENTS.md, CLAUDE.md, PR template, commit and sign-off format), work on a branch of the fork without opening any fork PR, write equivalence-first tests, run the upstream CI/CD checks locally before pushing (the fork will not run them), sign commits per the upstream DCO/CLA convention, and post the PR body — built from the upstream PR template — in a markdown pasteable format on the Multica issue. In review iterations (the PR is already open and a maintainer left review comments), address only the explicit requests on the same fork branch and post a pasteable PR comment per PR in the same fenced-markdown format; PR discussions — replies, resolutions, ambiguous asks — are left for the humans. Use whenever a Multica issue asks to "work on the contribution", "implement <candidate> in <owner/repo>", "prepare the branch for <repo>", "turn the scouted contribution into a PR-ready diff", or to "address the review comments on <PR>" — even if the issue only names the target repo and the change to make.