From 10891811c17ba3c54e26c09f2e87f9642e123886 Mon Sep 17 00:00:00 2001 From: Christopher Harrison Date: Wed, 4 Feb 2026 12:07:47 -0800 Subject: [PATCH 1/2] feat(skill): add make-repo-contribution skill Adds a new skill to help AI agents follow repository contribution guidelines when creating issues, commits, branches, and pull requests. Includes: - SKILL.md with comprehensive instructions - Issue template for when none exists in repo - PR template for when none exists in repo --- docs/README.skills.md | 1 + skills/make-repo-contribution/SKILL.md | 76 +++++++++++++++++++ .../assets/issue-template.md | 37 +++++++++ .../assets/pr-template.md | 36 +++++++++ 4 files changed, 150 insertions(+) create mode 100644 skills/make-repo-contribution/SKILL.md create mode 100644 skills/make-repo-contribution/assets/issue-template.md create mode 100644 skills/make-repo-contribution/assets/pr-template.md diff --git a/docs/README.skills.md b/docs/README.skills.md index bdb1c1551..229a5b6a9 100644 --- a/docs/README.skills.md +++ b/docs/README.skills.md @@ -36,6 +36,7 @@ Skills differ from other primitives by supporting bundled assets (scripts, code | [github-issues](../skills/github-issues/SKILL.md) | Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or manage issue workflows. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", or any GitHub issue management task. | `references/templates.md` | | [image-manipulation-image-magick](../skills/image-manipulation-image-magick/SKILL.md) | Process and manipulate images using ImageMagick. Supports resizing, format conversion, batch processing, and retrieving image metadata. Use when working with images, creating thumbnails, resizing wallpapers, or performing batch image operations. | None | | [legacy-circuit-mockups](../skills/legacy-circuit-mockups/SKILL.md) | Generate breadboard circuit mockups and visual diagrams using HTML5 Canvas drawing techniques. Use when asked to create circuit layouts, visualize electronic component placements, draw breadboard diagrams, mockup 6502 builds, generate retro computer schematics, or design vintage electronics projects. Supports 555 timers, W65C02S microprocessors, 28C256 EEPROMs, W65C22 VIA chips, 7400-series logic gates, LEDs, resistors, capacitors, switches, buttons, crystals, and wires. | `references/28256-eeprom.md`
`references/555.md`
`references/6502.md`
`references/6522.md`
`references/6C62256.md`
`references/7400-series.md`
`references/assembly-compiler.md`
`references/assembly-language.md`
`references/basic-electronic-components.md`
`references/breadboard.md`
`references/common-breadboard-components.md`
`references/connecting-electronic-components.md`
`references/emulator-28256-eeprom.md`
`references/emulator-6502.md`
`references/emulator-6522.md`
`references/emulator-6C62256.md`
`references/emulator-lcd.md`
`references/lcd.md`
`references/minipro.md`
`references/t48eeprom-programmer.md` | +| [make-repo-contribution](../skills/make-repo-contribution/SKILL.md) | All changes to code must follow the guidance documented in the repository. Before any issue is filed, branch is made, commits generated, or pull request (or PR) created, a search must be done to ensure the right steps are followed. Whenever asked to create an issue, commit messages, to push code, or create a PR, use this skill so everything is done correctly. | `assets/issue-template.md`
`assets/pr-template.md` | | [make-skill-template](../skills/make-skill-template/SKILL.md) | Create new Agent Skills for GitHub Copilot from prompts or by duplicating this template. Use when asked to "create a skill", "make a new skill", "scaffold a skill", or when building specialized AI capabilities with bundled resources. Generates SKILL.md files with proper frontmatter, directory structure, and optional scripts/references/assets folders. | None | | [markdown-to-html](../skills/markdown-to-html/SKILL.md) | Convert Markdown files to HTML similar to `marked.js`, `pandoc`, `gomarkdown/markdown`, or similar tools; or writing custom script to convert markdown to html and/or working on web template systems like `jekyll/jekyll`, `gohugoio/hugo`, or similar web templating systems that utilize markdown documents, converting them to html. Use when asked to "convert markdown to html", "transform md to html", "render markdown", "generate html from markdown", or when working with .md files and/or web a templating system that converts markdown to HTML output. Supports CLI and Node.js workflows with GFM, CommonMark, and standard Markdown flavors. | `references/basic-markdown-to-html.md`
`references/basic-markdown.md`
`references/code-blocks-to-html.md`
`references/code-blocks.md`
`references/collapsed-sections-to-html.md`
`references/collapsed-sections.md`
`references/gomarkdown.md`
`references/hugo.md`
`references/jekyll.md`
`references/marked.md`
`references/pandoc.md`
`references/tables-to-html.md`
`references/tables.md`
`references/writing-mathematical-expressions-to-html.md`
`references/writing-mathematical-expressions.md` | | [mcp-cli](../skills/mcp-cli/SKILL.md) | Interface for MCP (Model Context Protocol) servers via CLI. Use when you need to interact with external tools, APIs, or data sources through MCP servers, list available MCP servers/tools, or call MCP tools from command line. | None | diff --git a/skills/make-repo-contribution/SKILL.md b/skills/make-repo-contribution/SKILL.md new file mode 100644 index 000000000..3b7939df0 --- /dev/null +++ b/skills/make-repo-contribution/SKILL.md @@ -0,0 +1,76 @@ +--- +name: make-repo-contribution +description: All changes to code must follow the guidance documented in the repository. Before any issue is filed, branch is made, commits generated, or pull request (or PR) created, a search must be done to ensure the right steps are followed. Whenever asked to create an issue, commit messages, to push code, or create a PR, use this skill so everything is done correctly. +--- + +# Contribution guidelines + +Most every project has a set of contribution guidelines everyone needs to follow when creating issues, pull requests (PR), or otherwise contributing code. These may include, but are not limited to: + +- Creating an issue before creating a PR, or creating the two in conjunction +- Templates for issues or PRs that must be used depending on the change request being made +- Guidelines on what needs to be documented in those issues and PRs +- Tests, linters, and other prerequisites that need to be run before pushing any changes + +Always remember, you are a guest in someone else's repository. As such, you need to follow the rules and guidelines set forth by the repository owner when contributing code. + +## Using existing guidelines + +Before creating a PR or any of the steps leading up to it, explore the project to determine if there's any guidance. Places to explore include, but are not limited to: + +- README.md +- CONTRIBUTING.md +- Project documentation +- Issue templates +- Pull request or PR templates + +If any of those exist or you discover documentation elsewhere in the repo, read through what you find, consider it, and follow the guidance to the best of your ability. If you have any questions or confusion, ask the user for input on how best to proceed. DO NOT create a PR until you're certain you've followed the practices. + +## No guidelines found + +If no guidance is found, or doesn't provide guidance on certain topics, then use the following as a foundation for creating a quality contribution. **ALWAYS** defer to the guidance provided in the repository. + +## Tasks + +Many repository owners will have guidance on prerequisite steps which need to be completed before a PR is to be created. This can include, but is not limited to: + +- building the project or generating assets +- running linters and ensuring any issues are resolved +- naming guidelines and other patterns +- unit tests, end to end tests, or other tests which need to be created and pass + - related, there may be required coverage percentages + +Look through all guidance you find, and ensure any prerequisites have been satisfied. + +## Issue + +Always start by looking to see if an issue exists that's related to the task at hand. This may have already been created by the user, or someone else. If you discover one, prompt the user to ensure they want to use that issue, or which one they may wish to use. + +If no issue is discovered, look through the guidance to see if creating an issue is a requirement. If it is, use the template provided in the repository. If there are multiple, choose the one that most aligns with the work being done. If there are any questions, ask the user which one to use. + +If the requirement is to file an issue, but no issue template is provided, use [this issue template](./assets/issue-template.md) as a guide on what to file. + +## Branch + +Before performing any commits, ensure a branch has been created for the work. Follow whatever guidance is provided by the repository's documentation. If prefixes are defined, like `feature` or `chore`, or if the requirement is to use the username of the person making the PR, then use that. This branch must never be `main`, or the default branch, but should be a branch created specifically for the changes taking place. If no branch is already created, create a new one with a good name based on the changes being made and the guidance. + +## Commits + +When committing changes: + +1. Review all changes +2. Logically group the changes together +3. Create short commit messages for each group, following any guidance in the repository +4. Commit the grouped code to the branch. + +## Merging + +**NEVER** merge to main unless explicitly instructed to do so by the user + +## Pull request + +When creating a pull request, use existing templates in the repository if any exist, following the guidance you discovered. + +If no template is provided, use the [this PR template](./assets/pr-template.md). It contains a collection of headers to use, each with guidance of what to place in the particular sections. + +If an issue was created or is being used, ensure that issue is referenced in the PR. Use the `Closes #NUMBER` syntax to enable auto-closing of the issue. diff --git a/skills/make-repo-contribution/assets/issue-template.md b/skills/make-repo-contribution/assets/issue-template.md new file mode 100644 index 000000000..8f0b990ad --- /dev/null +++ b/skills/make-repo-contribution/assets/issue-template.md @@ -0,0 +1,37 @@ +# + +## Summary + + + +## Context + + + +## Proposed Solution + + + +## Acceptance Criteria + + + +## Additional Information + + diff --git a/skills/make-repo-contribution/assets/pr-template.md b/skills/make-repo-contribution/assets/pr-template.md new file mode 100644 index 000000000..4e6174752 --- /dev/null +++ b/skills/make-repo-contribution/assets/pr-template.md @@ -0,0 +1,36 @@ +# + +## Summary + + + +## Background + + + +## Changes + + + +## Testing + + + +## Additional Notes + + From 01e371fe328c3d519cdea3bdac191120fe953cad Mon Sep 17 00:00:00 2001 From: Christopher Harrison Date: Wed, 4 Feb 2026 14:09:40 -0800 Subject: [PATCH 2/2] fix(skill): correct formatting of description in make-repo-contribution skill --- skills/make-repo-contribution/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/make-repo-contribution/SKILL.md b/skills/make-repo-contribution/SKILL.md index 3b7939df0..c512d2320 100644 --- a/skills/make-repo-contribution/SKILL.md +++ b/skills/make-repo-contribution/SKILL.md @@ -1,6 +1,6 @@ --- name: make-repo-contribution -description: All changes to code must follow the guidance documented in the repository. Before any issue is filed, branch is made, commits generated, or pull request (or PR) created, a search must be done to ensure the right steps are followed. Whenever asked to create an issue, commit messages, to push code, or create a PR, use this skill so everything is done correctly. +description: 'All changes to code must follow the guidance documented in the repository. Before any issue is filed, branch is made, commits generated, or pull request (or PR) created, a search must be done to ensure the right steps are followed. Whenever asked to create an issue, commit messages, to push code, or create a PR, use this skill so everything is done correctly.' --- # Contribution guidelines