RepoCover
AI coding Skill · GitHub Social Preview

Create a distinctive cover for your code repository.

RepoCover reads the project first, then creates an editable 1280×640 cover instead of applying a template.

output / social-preview.png1280 × 640
RepoCover social preview showing project sources, cover design, and final checks
1280 × 640Best size for GitHub Social Preview
SVG + PNGEditable source and final raster
Under 1 MBWithin GitHub's Social Preview file-size limit
Where the cover appears

Help people recognize the repository wherever they find it.

One cover can introduce the project on GitHub, in its README, and wherever you share it.

Repository page

README

Place the cover near the top of the README so visitors can understand the project before reading the details.

Launch and sharing

Posts and promotion

Use it when announcing a project, sharing a release, posting on social media, or presenting your work in a portfolio.

Even a good repository is easy to overlook if people cannot understand it at a glance.

About

Many programmers are better at building than packaging their work. I am one of them.

As AI makes it easier to build more, a clear first impression may be what makes someone stop and look.

That is how RepoCover came to be. I made it in a day. It looked pretty good, so I started using it myself.

Visual direction

Choose the visual approach that fits the project.

RepoCover decides whether the interface, main visual, or existing images are suitable for a cover, then chooses what to preserve, recompose, or redesign.

Three situations RepoCover chooses the approach that fits what the project already has.
A

If the project already has a working product interface

Keep the recognizable interaction, crop around what matters, and remove browser chrome, debug clutter, or broken fragments.

B

If the project already has a brand or main visual

Keep its character, dimensionality, and color language, then rebuild the surrounding layout for a clearer cover.

C

If the project has no suitable image

Build the visual direction from what the project does and how it works, without inventing features.

How it works

Read first. Draw second.

01

Read the project

Review the README, key code, project rules, screenshots, and visuals already in the repository.

02

Check what is usable

Decide whether there is enough to make an honest cover, what to use, what is missing, and what should stay out.

03

Recompose

Keep the project's recognizable parts, remove clutter, and arrange the cover around one clear idea.

04

Check the result

The final SVG and PNG are reviewed at full size and as 320×160 thumbnails on both light and dark backgrounds.

Quick start

Install once. Use it right away.

Open your AI agent—Codex is recommended—and send it these two messages in order.

Message 1 · Install
Install the Skill from https://github.com/onovich/RepoCover.
Message 2 · Use
Use $repo-cover to create a cover for the current project.

RepoCover writes an editable SVG and exact 1280×640 PNG by default. It does not edit your README, upload the image, or change repository settings unless you ask separately.

Questions

What you may want to know.

Does it work without a screenshot?

Yes. RepoCover can derive a visual direction from what the repository contains, but it will not invent an interface or claim features it could not verify.

Can it use an existing web app?

Yes. An accessible local preview or working frontend usually produces the strongest result because the real interface can be inspected and selectively recomposed.

Does every cover look alike?

No. Every cover follows the same GitHub-ready output rules, but its subject, colors, dimensionality, and layout come from the current project.

Will it upload the image to GitHub?

Only when separately requested. Creating the files and changing repository settings are two different authorization boundaries.