Run any Skill in Manus with one click

issue-tracking-conventions

Stars31

Forks1

UpdatedApril 29, 2026 at 14:39

Use when creating, filing, writing, or revising issues, epics, initiatives, tasks, stories, enhancements, or bug reports in any tracker — GitHub Issues, Jira, Linear, GitLab, Asana, Shortcut. Covers structural conventions per issue type and self-containment rules for descriptions.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

kergoth

kergoth/dotfiles

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	issue-tracking-conventions
description	Use when creating, filing, writing, or revising issues, epics, initiatives, tasks, stories, enhancements, or bug reports in any tracker — GitHub Issues, Jira, Linear, GitLab, Asana, Shortcut. Covers structural conventions per issue type and self-containment rules for descriptions.

Issue Tracking Conventions

Personal defaults for writing issues, epics, and tickets. If a project's CONTRIBUTING, AGENTS.md, or issue templates mandate a different structure, follow the project.

By type

Epics / initiatives: outcome-level. Why it exists, what done looks like, what's explicitly excluded. No implementation details.
Tasks / stories / enhancements: definition of done, not how to implement.
Bugs: reproduction steps, expected vs. actual behavior.

Self-containment

Descriptions must be readable on their own. Don't reference local files, unlinked docs, branch names, or context the reader can't access.
If a related artifact exists (PR, design doc, prior issue, Slack thread), link to it explicitly with a descriptive label.
An issue should make sense to someone joining the project six months from now and reading it cold.

More from this repository

same repository

github-issue-triage

kergoth/dotfiles

Run end-to-end GitHub issue triage using the local triage scripts and parallel subagent scoring. Use when asked to create, refresh, or rerun issue triage markdown with complexity, difficulty, benefit, scope, and execution-lane recommendations (`agent-implementation`, `agent-assist-human`, `human-only`).

2026-07-0731

find-session

kergoth/dotfiles

Find and resume a past Claude Code, Codex, or Cursor Agent conversation by searching session history files by keyword. Use this skill whenever the user wants to find a previous conversation, can't remember which directory or agent they were using, wants to look up work from a past session, needs to resume a session they can't locate with /resume, codex resume, or agent --resume, or says something like "I know we discussed X somewhere" or "where was that session about Y". Infers search scope, agent, and keywords from the user's description and presents matching sessions with summaries before asking which to resume. Always use this skill rather than manually searching ~/.claude/, ~/.codex/, or ~/.cursor/ yourself.

2026-06-3031

git-commits

kergoth/dotfiles

Use for commit-level Git workflows in non-`.jj/` repositories: stage one logical change, write or revise commit messages, amend, create fixup commits, split bundled edits, curate history with rebase or autosquash, and verify bisectability. In repositories containing `.jj/`, use this skill only for explicit Git-only commit intent; generic commit intent routes to `jujutsu` plus `jj-commits`. Trigger on requests such as "commit this", "check it in", "ship it", "stage and commit", "amend", "fixup", "clean up history", "reword/split commits", or "draft/rewrite the commit message". Also use for indirect commit-message creation when drafting plans that specify commits (including `superpowers:writing-plans` outputs), and when writing commit message text in design docs, PR notes, or other artifacts.

2026-05-2931

cli-design

kergoth/dotfiles

Guidelines for designing and implementing command-line interfaces. Use when creating a new CLI tool, adding subcommands or flags to an existing one, implementing help text, designing error messages, or structuring CLI output. Also use when reviewing CLI code for usability, when the user asks about CLI best practices, or when generating argument parsers, config handling, or shell completions. Applies to any language.

2026-05-0531

shell-script-style

kergoth/dotfiles

Apply Christopher Larson's preferred Bash and POSIX shell script style when creating or substantially editing user-facing shell scripts. Use when writing or modifying shell utilities under `scripts/` or `script/` (including extensionless shebang executables, pre-commit entry scripts, and CI helpers), `.sh` files, shell snippets intended for the user to keep, or any Bash or POSIX sh program that will become part of the maintained codebase. Do not use for temporary test scripts, disposable intermediate artifacts, or scripts written solely for AI-agent execution.

2026-05-0431

jj-commits

kergoth/dotfiles

Use for generic commit-related intent in `.jj/` repositories. Must be paired with `jujutsu` in the same turn; never use it as a standalone skill. Explicit Git-only `.jj` commit intent routes to `git-commits`.

2026-05-0131