skills/issues/SKILL.md
Route issue management to the right tracker based on GitHub org — Linear for work, GitHub Issues for OSS and personal repos
npx skillsauth add athal7/dotfiles issuesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Route to the correct issue tracker based on the GitHub remote org.
git remote get-url origin
orgs.<org>.issues)."linear" → use the linear-cli skill.gh issue commands.The project body (inline editor in the UI) is the documentContent.content field — not the legacy description field. Read it via:
linear api '{ project(id: "PROJECT_UUID") { documentContent { content } } }'
Write it via projectUpdate with the content field — the UI may need a hard refresh to show the update:
linear api --variable projectId=PROJECT_UUID --variable content=@/tmp/content.md << 'GRAPHQL'
mutation($projectId: String!, $content: String!) {
projectUpdate(id: $projectId, input: { content: $content }) {
success
}
}
GRAPHQL
Note: linear document create --project creates an attached document (Documents tab), not the inline body. linear document update --content-file is broken (schpet/linear-cli#153).
Both trackers have templates configured outside this skill. Read the relevant one before authoring an issue, project, or status update so the artifact matches the established shape; don't invent your own structure.
Linear: templates are configured in the workspace and applied automatically in the web UI. The CLI doesn't apply them — fetch the template content and follow it manually:
# List templates available to you
linear api '{ templates { id name type team { key } } }'
# Get the content of a specific template
linear api --variable id=TEMPLATE_UUID '{ template(id: $id) { name templateData } }'
GitHub: templates live in the repo at .github/ISSUE_TEMPLATE/*.md and .github/pull_request_template.md. gh issue create --template <name> only works in interactive mode; for non-interactive use, read the template file directly and pass content via --body-file.
development
Zoom meeting captions — file locations and format
tools
macOS dictation custom vocabulary — sync knowledge base names and terms to the system spelling dictionary
testing
Look up people, projects, products, and decisions locally first: contact info (email, Slack ID, GitHub handle), titles and teams, project/product status, who works on what, and past decisions. Check before searching Slack, email, calendar, or GitHub — this is the first stop for any contact detail, project context, or decision-history question.
testing
Communication style, audience awareness, and AI-authorship markers for human-facing prose — load when composing chat messages, review comments, merge request descriptions, emails, doc bodies, or ticket descriptions