create-vercel-ai-issue
Skill1.2k starsChanged 21 days agoApache-2.0View on GitHub
Create a well-formed GitHub issue in vercel/ai using the gh CLI. Use when reporting an AI SDK bug or preparing an issue body that contains logs, code blocks, versions, reproduction steps, and shell-sensitive text.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Put complex Markdown in a temporary body file so shell interpolation cannot alter backticks or code blocks.
- Distinctive: line 14
Do not create the external issue unless the user has authorized that write.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create a vercel/ai issue
- Confirm
gh auth statusand inspectvercel/aibefore writing. - Prepare a focused issue with sections for the problem, exact error, package versions, minimal reproduction, expected behavior, and actual behavior.
- Put complex Markdown in a temporary body file so shell interpolation cannot alter backticks or code blocks.
- Run
gh issue create -R vercel/ai --title "<title>" --body-file <file>. - Return the created issue URL.
Do not create the external issue unless the user has authorized that write.
Trending
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Other versions2 projects use a version of this.
Word for word · 2
- FranciscoMoretti/chat-js★ 1.2k100% same
- FranciscoMoretti/sparka★ 1.2k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- check-visual-changesSkill
- dev-auth-bypassSkill
- economical-visual-testsSkill
- generate-code-snippetSkill
- lazy-prefetch-patternSkill
- making-ui-changesSkill
- next-cache-components-adoptionSkill
- next-dev-loopSkill
- next-partial-prefetching-adoptionSkill
- review-docsSkill
- strategic-testingSkill
- triage-visual-changesSkill
- trpc-patternsSkill
- vitest-visual-testingSkill
- worktree-portsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.