Create Issue
tradingstrategy-ai/frontend
Creates a new GitHub issue with structured user story format, acceptance criteria, and project integration.
Produce a verified spec — problem, desired outcome, and acceptance criteria — before building.
Install Spec
$ npx skills add getsentry/sentry-react-native --skill spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install getsentry/sentry-react-native spec --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/getsentry/sentry-react-native.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/spec .claude/skills/spec && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "spec" agent skill from https://github.com/getsentry/sentry-react-native/tree/main/.agents/skills/spec into .claude/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/getsentry/sentry-react-native/tree/main/.agents/skills/specType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add getsentry/sentry-react-native --skill spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install getsentry/sentry-react-native spec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/sentry-react-native.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/spec .agents/skills/spec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "spec" agent skill from https://github.com/getsentry/sentry-react-native/tree/main/.agents/skills/spec into .agents/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getsentry/sentry-react-native --skill spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install getsentry/sentry-react-native spec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/sentry-react-native.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/spec .cursor/skills/spec && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "spec" agent skill from https://github.com/getsentry/sentry-react-native/tree/main/.agents/skills/spec into .cursor/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/getsentry/sentry-react-native.git --path .agents/skills/spec--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add getsentry/sentry-react-native --skill spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install getsentry/sentry-react-native spec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/sentry-react-native.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/spec .gemini/skills/spec && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "spec" agent skill from https://github.com/getsentry/sentry-react-native/tree/main/.agents/skills/spec into .gemini/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install getsentry/sentry-react-native specInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add getsentry/sentry-react-native --skill spec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/getsentry/sentry-react-native.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/spec .github/skills/spec && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "spec" agent skill from https://github.com/getsentry/sentry-react-native/tree/main/.agents/skills/spec into .github/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getsentry/sentry-react-native --skill spec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install getsentry/sentry-react-native spec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/sentry-react-native.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/spec .opencode/skills/spec && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "spec" agent skill from https://github.com/getsentry/sentry-react-native/tree/main/.agents/skills/spec into .opencode/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
spec- GitHub stars
- 1.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 602 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Produce a verified spec — problem, desired outcome, and acceptance criteria — before building.
- Works in 6 steps: Establish the source → Reconstruct the real intent → Check the premise against the code → …
- Given a GitHub/Linear issue link
- SKILL.md covers 1. Establish the source, 2. Reconstruct the real intent, 3. Check the premise against… and 4. Grill the gaps, plus 2 more sections
- Calls gh
What it does
Spec is an agent skill from getsentry/sentry-react-native, published by the product's own GitHub organization. Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the what isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering User stories and Cross-platform mobile apps. It works with Sentry, GitHub and Linear. The repository describes itself as: Official Sentry SDK for React Native. The licence is MIT.
When your agent uses it
- Given a GitHub/Linear issue link
- Starting from a fuzzy in-conversation idea
- Asked to figure out what to do / scope this / what should I build — whenever the what isnt yet pinned down
Example prompts
- “figure out what to do”
- “scope this”
- “what should I build”
- “/spec”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 6ce1083. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Spec loads about 1.1k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 602 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from getsentry/sentry-react-native at commit 6ce1083, republished under its MIT licence (© getsentry). 602 words, ~1,096 tokens.
Download SKILL.mdSave it as
.claude/skills/spec/SKILL.md (or your agent's skills folder).- name
- spec
- description
- Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.
Settle what to build and why — with verifiable acceptance criteria — before any design or code. This is the front of the pipeline: spec (what) → design-first (how) → code-guidelines + test-guidelines (build) → review (which verifies the result against this spec).
Run it for a tracked issue or a fuzzy ask. Skip it — and say so — when the ask is already a precise, verifiable instruction.
1. Establish the source
Get the raw intent from wherever it lives:
- From a tracked issue (a GitHub/Linear link) — fetch it, don't work from the link text or your memory of it:
- GitHub:
gh issue view <url-or-number> --json title,body,comments,labels,state, plus any linked PRs. - Linear: the Linear tools — the issue and its comments. Sentry SDK issues often carry a Linear backlink (e.g.
RN-###) in a comment. - Read the full body, every comment, labels, and linked issues/PRs. The real decision is often buried in a comment, not the title.
- GitHub:
- From an in-conversation idea — start from what the user said, in their words. If a tracked issue might exist, ask for the link; otherwise proceed — the spec itself is the source of truth.
Either way you now hold the raw intent — usually vague. Sharpen it below.
2. Reconstruct the real intent
The raw ask usually names a symptom; the real need is underneath. State, in the domain's own words: the problem this solves, who it's for (SDK user? a downstream SDK like Flutter/.NET that depends on the native layer?), and what "done" looks like. Separate the reported symptom from the underlying need — they're often not the same fix.
3. Check the premise against the code
The ask may be stale, partial, or wrong. Investigate before believing it:
- Does the described behavior actually exist / reproduce? For a bug, find the code path — and if it's non-trivial, build the repro loop now (see diagnosing-bugs).
- Is part of it already implemented, or made moot by a later change (an RN/native-SDK bump, a new arch path)?
- Does the codebase contradict the issue's assumptions? Check both JS and the relevant native side.
- Does it touch the public API surface (barrel / options) or the bridge ABI? That raises the stakes and the review bar.
Surface any contradiction to the user before going further — a spec built on a false premise wastes the whole pipeline.
Show full SKILL.md (226 more words)Show less
4. Grill the gaps
Interview relentlessly until the intent is unambiguous. One question at a time, waiting for the answer before the next — batching is bewildering. Give your recommended answer with each question. If a question can be answered by reading the code, read it instead of asking. Drive out scope, edge cases, and the in-vs-out boundary — for this SDK that usually includes: which platforms/architectures are in scope, whether it's opt-in or default-on, PII implications, and whether downstream SDKs are affected.
5. Write the spec and get sign-off
Produce, in the conversation:
- Problem — what's wrong or missing, and why it matters.
- Outcome — the desired end state, in the domain's words.
- Acceptance criteria — verifiable, observable conditions (e.g. "an event captured with X carries attribute Y on both New and Old Architecture"; "the native module missing → SDK returns a fallback, no throw"). This is the bar
review's Spec axis checks against. - Non-goals — what's explicitly out of scope (platforms, arch, options deferred).
- Open questions — anything still unresolved.
Done when the user signs off on the acceptance criteria — explicit agreement that meeting them means the work is complete. Not "looks reasonable"; agreement on the bar.
6. Hand off
The what is now settled. This spec becomes the PR description's problem / outcome / acceptance at ship time, and review's Spec axis verifies against it. Hand off to design-first to shape the how.
© getsentry, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/spec of getsentry/sentry-react-native.
Open the folder on GitHubat commit 6ce1083
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in getsentry/sentry-react-native, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Spec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Spec this skillgetsentry/sentry-react-native | 1.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Create Issuetradingstrategy-ai/frontend | 150 | — | ~607 | Automated safety check: Pass | None | |
| Superset Automatesuperset-sh/superset | 15k | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Reviewgetsentry/sentry-dart | 873 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Run GitHub Projectchrisbanes/skills | 1.1k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Abo Issue Watcherjeeftor/audiobook-organizer | 189 | — | ~417 | Automated safety check: Pass | MIT |
Similar skills
Superset Automate
superset-sh/superset
Turns a recurring chore into a scheduled or event-triggered Superset agent, drafting its prompt, picking a target and trigger, and reviewing the first run.
- Official
Review
getsentry/sentry-dart
Three-axis review of the branch diff — Standards (this repo's documented standards + public API surface), Spec (the originating Linear issue / PR), and Correctness (runtime bugs + the SDK threat…
Run GitHub Project
chrisbanes/skills
A skill your agent uses when asked to set up, review, or operate a repository's GitHub Project workflow, including ready claims, role-labelled human work, unknown remote mutation outcomes, Todo…
Abo Issue Watcher
jeeftor/audiobook-organizer
Inspect Audiobook Organizer GitHub issues, comments, acceptance criteria, linked PRs, and next steps.
Specify
RafaelGB/Obsidian-ZettelFlow
Stage 1 of the SDD pipeline — write a ZettelFlow spec into a GitHub issue body (problem, value, functional requirements, testable acceptance criteria, capability disclosure, out-of-scope).
More from getsentry/sentry-react-native
- Official
Code Guidelines
getsentry/sentry-react-native
Enforce Sentry React Native SDK code guidelines for implementation, refactoring, and review.
- Official
Test Guidelines
getsentry/sentry-react-native
Enforce Sentry React Native SDK test conventions for naming, structure, mocking, and fixtures with Jest.
- Official
Review
getsentry/sentry-react-native
Three-axis review of the branch diff — Standards (this repo's documented standards + public API/bridge surface), Spec (the originating Linear/GitHub issue or PR), and Correctness (runtime bugs + the…
- Official
Design First
getsentry/sentry-react-native
Shape non-trivial work before writing it — decide the modules, the seams, and the public API surface up front.
- Official
Diagnosing Bugs
getsentry/sentry-react-native
A discipline for hard bugs, flaky tests, CI hangs, native crashes, and performance regressions in this SDK.
Related
Categories
Questions about Spec
What does Spec do?
Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Spec is an agent skill from getsentry/sentry-react-native, published by the product's own GitHub organization. Produce a verified spec — problem, desired outcome, and acceptance criteria — before building.
When should I use Spec?
Spec fits situations like: given a GitHub/Linear issue link; starting from a fuzzy in-conversation idea; asked to figure out what to do / scope this / what should I build — whenever the what isnt yet pinned down.
How do I install Spec in Claude Code?
Run `npx skills add getsentry/sentry-react-native --skill spec -a claude-code`. Or copy the skill folder (.agents/skills/spec in getsentry/sentry-react-native) into .claude/skills/spec in your project. Claude Code loads it when a task matches its description.
How do I install Spec in Codex?
Run `npx skills add getsentry/sentry-react-native --skill spec -a codex`. Or copy the skill folder (.agents/skills/spec in getsentry/sentry-react-native) into .agents/skills/spec in your project. Codex loads it when a task matches its description.
Can I use Spec in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getsentry/sentry-react-native --skill spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spec, .gemini/skills/spec, .github/skills/spec and .opencode/skills/spec in your project.
What does Spec need to run?
Going by SKILL.md and its folder, Spec needs the command-line tools its instructions call (gh).
Does Spec access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Spec safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Spec use?
Spec is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Spec use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Spec?
Skills that share tags, products or a category with Spec: Create Issue (tradingstrategy-ai/frontend, 150 stars), Superset Automate (superset-sh/superset, 15k stars), Review (getsentry/sentry-dart, 873 stars) and Run GitHub Project (chrisbanes/skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Spec?
getsentry (a GitHub organization, an official publisher) maintains it in getsentry/sentry-react-native, which has 1,824 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.
Source: getsentry/sentry-react-native on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.