New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Shift Issue Writer

by shift-editor in shift-editor/shift

Sets the rules for finding, writing and updating Shift GitHub issues: search for duplicates first, use outcome-focused titles and testable acceptance criteria.

Apache-2.0Auto-check passedDevelopment

Install Shift Issue Writer

skills CLI
$ npx skills add shift-editor/shift --skill issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install shift-editor/shift issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/shift-editor/shift.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/issue .claude/skills/issue && rm -rf skills-src

Use ~/.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/

Facts

Skill name
issue
GitHub stars
347
Token cost
~1.4k tokens
SKILL.md length
706 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
Apache-2.0

At a glance

Sets the rules for finding, writing and updating Shift GitHub issues: search for duplicates first, use outcome-focused titles and testable acceptance criteria.

  • Works in 7 steps: Confirm the requested problem or outcome. → Search open and closed issues with… → Inspect likely matches and decide… → …
  • Filing a new bug or feature issue for the Shift repository
  • SKILL.md covers Search before creation, Title, Body and Pull request linkage, plus 2 more sections
  • Calls gh

What it does

Issues in the Shift font editor repository follow one set of rules. Before anything is created, the agent runs several short searches across open and recently closed issues, reuses a matching open one instead of filing a duplicate, links related issues, and inspects closed matches to judge whether a report is a recurrence, a regression or distinct work.

Titles state the missing or incorrect behavior in direct words, stay near 72 characters, and skip trailing punctuation, emoji and agent labels. Bodies stay small, with a problem statement and acceptance criteria that describe observable behavior rather than vague claims such as works correctly. UI defects get screenshots or recordings uploaded as GitHub attachments, with private data redacted and mockups labeled as proposals.

Closed issues are never reopened or changed without your explicit approval. The skill also covers when substantial work needs an issue before a pull request and how the pull request closes it.

When your agent uses it

  • Filing a new bug or feature issue for the Shift repository
  • Checking whether an issue already exists before opening another
  • Updating or triaging an existing issue and tightening its acceptance criteria
  • Substantial work is about to start and needs an issue before the pull request

Example prompts

  • “File an issue for the glyph canvas flickering when zooming, and check for duplicates first.”
  • “Search for existing issues about kerning pair import before I open a new one.”
  • “Rewrite the acceptance criteria on the undo history issue so each one is observable.”

Requirements

  • Access to the Shift repository's GitHub issues

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Confirm the requested problem or outcome.
  2. Search open and closed issues with multiple focused queries.
  3. Inspect likely matches and decide whether to reuse, reference, or create.
  4. Draft a concise title and body with verifiable acceptance criteria.
  5. Check for credentials, private user data, unsupported claims, and accidental implementation commitments.
  6. Create the issue with an explicit repository and a body file when requested or required for substantial pull-request work.
  7. Return the issue URL, title, and any relationship to existing issues.

What it can do on your machine

Read from SKILL.md and the folder at commit 6ade7f2. 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

Shift Issue Writer loads about 1.4k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 706 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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 shift-editor/shift at commit 6ade7f2, republished under its Apache-2.0 licence (© shift-editor). 706 words, ~1,371 tokens.

Download SKILL.mdSave it as .claude/skills/issue/SKILL.md (or your agent's skills folder).
name
issue
description
Canonical rules for finding, creating, and updating Shift GitHub issues. Use whenever the user asks to file, create, open, update, triage, or search for an issue, or when substantial work needs an issue before a pull request. Prevents duplicates and defines acceptance criteria and pull-request closure semantics.

/issue — How Shift issues are written

An issue records an unmet product or engineering outcome. It explains the problem and the truth that must become observable without prescribing an unnecessary implementation.

Search before creation

Always search open and recently closed issues before creating one. Use several concise searches based on the user-visible behavior, domain terms, and likely title wording.

  • Reuse a matching open issue rather than creating a duplicate.
  • Reference a related issue when the scope overlaps but is not identical.
  • Inspect a matching closed issue before deciding whether the new report is a recurrence, a regression, or distinct work.
  • Never reopen or modify a closed issue without explicit user approval.

If an existing issue is adequate, return or update that issue instead of creating another.

Title

Use a concise outcome-oriented title that stands alone in issue lists. The title should:

  • describe the missing or incorrect behavior;
  • use direct, specific wording;
  • stay at or below 72 characters when practical;
  • omit trailing punctuation, emoji, agent labels, and implementation trivia.

Issues do not require a Conventional Commit prefix. Use fix:, feat:, or another type only when it is already part of an established issue series.

Body

Use the smallest body that makes the work testable:

markdown
## Problem

What is missing, broken, unsafe, or difficult, and why it matters.

## Expected outcome

What should be observably true when the issue is complete.

## Acceptance criteria

- [ ] concrete, verifiable result
- [ ] important safety or compatibility boundary

Add reproduction steps, evidence, constraints, or out-of-scope notes only when they materially clarify the issue. Do not copy an implementation plan into the issue unless the implementation boundary itself is a requirement.

Acceptance criteria must describe behavior or durable repository outcomes. Do not use vague criteria such as “works correctly,” “tests pass,” or “code is clean.”

UI evidence

For UI defects or visual-change requests whose appearance matters, attach screenshots or recordings when the affected state can be reproduced safely.

  • Show the actual affected UI and the state that demonstrates the problem or review need.
  • Prefer GitHub user attachments over committing issue-only media to the repository.
  • Redact private user data, credentials, and sensitive documents before uploading.
  • Label conceptual mockups as proposals; never present them as the current implementation.
  • If useful evidence cannot be captured safely or reliably, state why instead of fabricating it.

Do not require visual evidence when the issue has no visible review surface.

Pull request linkage

Issue state has these meanings:

  • Open: at least one accepted outcome remains unmet.
  • Closed by merge: a pull request containing Closes #N merged to the default branch and fully satisfied the issue.
  • Referenced: a pull request containing Refs #N contributes context or partial work; the issue remains open.
  • Reopened: a human explicitly determined that the accepted outcome was not met or regressed.

Use Closes #N only when the pull request satisfies the complete issue. Use Refs #N for partial work, investigation, prerequisites, or related context.

Show full SKILL.md (260 more words)Show less

Creation process

  1. Confirm the requested problem or outcome.
  2. Search open and closed issues with multiple focused queries.
  3. Inspect likely matches and decide whether to reuse, reference, or create.
  4. Draft a concise title and body with verifiable acceptance criteria.
  5. Check for credentials, private user data, unsupported claims, and accidental implementation commitments.
  6. Create the issue with an explicit repository and a body file when requested or required for substantial pull-request work.
  7. Return the issue URL, title, and any relationship to existing issues.

A request to create or file an issue authorizes the corresponding gh issue create. It does not authorize changing repository settings, labels, milestones, projects, assignees, or issue state unless the user explicitly asks.

Hard rules

  • Never create a duplicate merely to give a pull request something to close.
  • Never fabricate reproduction steps, logs, acceptance criteria, labels, milestones, or relationships.
  • Never include credentials, signing material, tokens, private paths, or sensitive user documents.
  • Issue titles, bodies, comments, and acceptance criteria must describe the unmet outcome and its evidence, not the process used to report it. Never include incidental execution metadata such as agent identity, handoff mechanics, remote hosts, machine names, tmux sessions, worktree paths, or “finishing work off.” Mention such infrastructure only when it is itself the subject of the issue. Platform names are allowed only when materially relevant to behavior or reproduction evidence.
  • Never close or reopen an issue without explicit authorization or the approved Closes #N merge transition.
  • Never claim that a pull request fully resolves an issue when acceptance criteria remain unmet.

© shift-editor, Apache-2.0. 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 .codex/skills/issue of shift-editor/shift.

Open the folder on GitHubat commit 6ade7f2

Compare with similar skills

Shift Issue Writer 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.

Shift Issue Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Shift Issue Writer this skillshift-editor/shift347—~1.4kAutomated safety check: PassApache-2.0
Exposed Bug Fix WorkflowJetBrains/Exposed9.3k—~3.8kAutomated safety check: PassApache-2.0
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
Ouroboros Maintainer TriageQ00/ouroboros6.2k—~1.7kAutomated safety check: PassMIT
PR Triagertk-ai/rtk83k—~2.5kAutomated safety check: NotesApache-2.0
Read-Only GitHub Triagecode-yeongyu/oh-my-openagent70k—~4.3kAutomated safety check: PassCustom licence

Similar skills

  • Exposed Bug Fix Workflow

    JetBrains/Exposed

    Official

    Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.

    9.3k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Ouroboros Maintainer Triage

    Q00/ouroboros

    Triages and works through GitHub issues and pull requests in the Q00/ouroboros repo as a maintainer, within a stated review boundary and clear limits on what it may change.

    6.2k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed

  • PR Triage

    rtk-ai/rtk

    Audits a repository's open pull requests, deep-reviews chosen ones and drafts review comments that are only posted after you approve them.

    83k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: notes

  • Read-Only GitHub Triage

    code-yeongyu/oh-my-openagent

    Fans out one background subagent per open GitHub issue or pull request to write an evidence-backed report, never commenting, closing or merging anything.

    70k GitHub stars~4.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Qwen Code Issue and PR Triage

    QwenLM/qwen-code

    Gatekeeps GitHub issues and pull requests for Qwen Code maintainers through staged static reviews that post a comment after each stage, under strict safety rules.

    28k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed

More from shift-editor/shift

All 14 skills in this repo

  • Shift Commit Rules

    shift-editor/shift

    Rules for writing git commits in the Shift font editor repo: Conventional Commits subjects, user-facing changelog wording, concise subjects and logical commit boundaries.

    347 GitHub stars~1.4k tokensUpdated today
    Auto-check: notes

  • Dead Code Removal with Knip

    shift-editor/shift

    Finds unused files, exports and class members with Knip, then verifies each candidate through reference tracing before removing anything, never using knip --fix.

    347 GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Shift Subsystem Docs

    shift-editor/shift

    Updates or creates DOCS.md files for Shift subsystems, recording the architecture invariants and constraints that cannot be learned from reading the source.

    347 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Adversarial Docs Audit

    shift-editor/shift

    Fact-checks DOCS.md files against the source code, testing each concrete claim and sorting it as true, false, stale or unverifiable.

    347 GitHub stars~818 tokensUpdated today
    Auto-check passed

  • Shift JSDoc Contracts

    shift-editor/shift

    Guides writing JSDoc for Shift exported APIs as a stable caller contract, covering ownership, lifetime, side effects and nullability that TypeScript types cannot express.

    347 GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • Shift Pull Request Rules

    shift-editor/shift

    Rules for preparing, opening and updating pull requests in the Shift repository: Conventional Commit titles, Release Please effects, evidence-based bodies and UI screenshots.

    347 GitHub stars~2.1k tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Shift Issue Writer

What does Shift Issue Writer do?

Sets the rules for finding, writing and updating Shift GitHub issues: search for duplicates first, use outcome-focused titles and testable acceptance criteria. Issues in the Shift font editor repository follow one set of rules. Before anything is created, the agent runs several short searches across open and recently closed issues, reuses a matching open one instead of filing a duplicate, links related issues, and inspects closed matches to judge whether a report is a recurrence, a regression or distinct work.

When should I use Shift Issue Writer?

Shift Issue Writer fits situations like: filing a new bug or feature issue for the Shift repository; checking whether an issue already exists before opening another; updating or triaging an existing issue and tightening its acceptance criteria; substantial work is about to start and needs an issue before the pull request.

How do I install Shift Issue Writer in Claude Code?

Run `npx skills add shift-editor/shift --skill issue -a claude-code`. Or copy the skill folder (.codex/skills/issue in shift-editor/shift) into .claude/skills/issue in your project. Claude Code loads it when a task matches its description.

How do I install Shift Issue Writer in Codex?

Run `npx skills add shift-editor/shift --skill issue -a codex`. Or copy the skill folder (.codex/skills/issue in shift-editor/shift) into .agents/skills/issue in your project. Codex loads it when a task matches its description.

Can I use Shift Issue Writer 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 shift-editor/shift --skill issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue, .gemini/skills/issue, .github/skills/issue and .opencode/skills/issue in your project.

What does Shift Issue Writer need to run?

Going by SKILL.md and its folder, Shift Issue Writer needs the command-line tools its instructions call (gh). Our summary lists: Access to the Shift repository's GitHub issues.

Does Shift Issue Writer 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 Shift Issue Writer 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 Shift Issue Writer use?

Shift Issue Writer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Shift Issue Writer use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Shift Issue Writer?

Skills that share tags, products or a category with Shift Issue Writer: Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars), Pre-Release PR Triage (jamiepine/voicebox, 57k stars), Ouroboros Maintainer Triage (Q00/ouroboros, 6.2k stars) and PR Triage (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Shift Issue Writer?

shift-editor (a GitHub organization) maintains it in shift-editor/shift, which has 347 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.

Source: shift-editor/shift on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.