implementing-issues

Étoiles9

Forks1

Mis à jour8 mai 2026 à 00:24

Implement a GitHub or Linear issue end-to-end with TDD, branch management, and PR creation. Use when implementing an issue, working on a ticket, starting a feature from an issue, or building from issue requirements.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

TrevorS

TrevorS/dot-claude

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	implementing-issues
description	Implement a GitHub or Linear issue end-to-end with TDD, branch management, and PR creation. Use when implementing an issue, working on a ticket, starting a feature from an issue, or building from issue requirements.
argument-hint	<issue number, #number, or TEAM-ID>

Implementing Issues

Work through an issue with TDD, proper branch management, and PR creation.

Workflow

Auto-detect VCS -- jj root succeeds -> jj, otherwise git
Auto-detect issue tracking -- numeric/#number -> GitHub (gh), TEAM-ID format -> Linear (linear-cli)
Check working copy status -- ensure not on main/master/dev
Create feature branch with proper naming
Read and understand issue requirements
Review project context -- spec.md, requirements.md, CLAUDE.md
Follow TDD -- write tests first
Implement minimal code to pass tests
Refactor incrementally while maintaining coverage
Clean up history -- squash/curate commits
Push with upstream tracking and create PR
Write complete PR description with test plan

Branch Naming

GitHub: feature/issue-{number}-{short-description} or fix/issue-{number}-{description}
Linear: feature/{team-id}-{short-description} or fix/{team-id}-{description}

Branch Safety

jj:

jj log -r @ --no-graph -T 'bookmarks'
# If on main, create new change:
jj new main -m "feat: description"
jj git fetch

git:

git branch --show-current
# If on protected branch, create feature branch:
git checkout -b "feature/issue-<number>-<description>"
git fetch origin

Implementation Standards

Write failing tests first capturing acceptance criteria
Implement minimal code to make tests pass
Refactor while maintaining green tests
Follow project patterns from CLAUDE.md
Add meaningful comments for complex logic
Update docs if public APIs change

Push and PR

jj:

jj squash -m "feat: final commit message"
jj bookmark set <branch> -r @
jj git push --bookmark <branch>

git:

git push -u origin HEAD

PR creation:

gh pr create --title "[Issue #<number>] Title" --body "$(cat <<'EOF'
## Summary
<bullets>

## Test plan
- [ ] Tests pass
- [ ] Manual verification
EOF
)"

Command Reference

# GitHub
gh issue view <number> --json title,body,labels,assignees,milestone
gh pr create --title "title" --body "body"

# Linear
linear-cli issues
linear-cli issue <team-id>

Plus depuis ce dépôt

même dépôt

syncing-claude-config

TrevorS/dot-claude

Sync this Claude Code config against new release notes — find config features added since the pinned baseline that this config should adopt. Use when Claude Code has been updated, when the user asks what's new / what changed / whether to adopt new settings or hooks, after a version bump, or when checking config currency against the latest release. Reports adoptable settings/hooks/env-vars/permissions as a risk-tiered proposal, then bumps the baseline. Do NOT use for auditing existing config quality, debugging hooks, or organizing rules — that is `maintaining-claude-code`.

2026-07-309

monitoring-ci

TrevorS/dot-claude

Monitor and watch GitHub Actions CI/CD pipeline runs in real time. Use when the user has pushed code and wants to watch the build, check CI status, see if tests passed, monitor a pipeline, or wait for a workflow run to complete. Also use after any `jj git push` or `git push` command. Reports pass/fail with failed job logs. Do NOT use for writing or editing CI workflow YAML files, optimizing CI config, or debugging CI configuration — only for monitoring active runs.

2026-07-309

cleaning-commit-history

TrevorS/dot-claude

Reorganize and clean up messy commit history on a feature branch into logical, reviewable commits. Use when cleaning up commits, preparing a branch for review, separating formatting from logic changes, fixing broken intermediate states, or squashing WIP commits.

2026-07-309

maintaining-claude-code

TrevorS/dot-claude

Audit and improve Claude Code hooks, rules, and settings.json. Use when adding/debugging a hook, organizing rules, auditing settings.json (permissions, env vars, stale flags), or deciding between hook vs skill vs rule vs CLAUDE.md. For SKILL.md authoring use the skill-creator plugin; for CLAUDE.md audits use the claude-md-improver plugin.

2026-06-019

executing-test-plans

TrevorS/dot-claude

Execute a structured test plan and emit a concise results document (JSON + Markdown). Use when running test plans, executing QA workflows, verifying acceptance criteria systematically, or producing test results documentation.

2026-06-019

searching-history

TrevorS/dot-claude

Search past Claude Code sessions to recall prior solutions, commands, fixes, and decisions. Use when the user references earlier work ("how did I fix", "last time we", "pick up where we left off", "a few months ago", "what was that … I set up", "didn't I once").

2026-06-019

name	implementing-issues
description	Implement a GitHub or Linear issue end-to-end with TDD, branch management, and PR creation. Use when implementing an issue, working on a ticket, starting a feature from an issue, or building from issue requirements.
argument-hint	<issue number, #number, or TEAM-ID>

Implementing Issues

Work through an issue with TDD, proper branch management, and PR creation.

Workflow

Auto-detect VCS -- jj root succeeds -> jj, otherwise git
Auto-detect issue tracking -- numeric/#number -> GitHub (gh), TEAM-ID format -> Linear (linear-cli)
Check working copy status -- ensure not on main/master/dev
Create feature branch with proper naming
Read and understand issue requirements
Review project context -- spec.md, requirements.md, CLAUDE.md
Follow TDD -- write tests first
Implement minimal code to pass tests
Refactor incrementally while maintaining coverage
Clean up history -- squash/curate commits
Push with upstream tracking and create PR
Write complete PR description with test plan

Branch Naming

GitHub: feature/issue-{number}-{short-description} or fix/issue-{number}-{description}
Linear: feature/{team-id}-{short-description} or fix/{team-id}-{description}

Branch Safety

jj:

jj log -r @ --no-graph -T 'bookmarks'
# If on main, create new change:
jj new main -m "feat: description"
jj git fetch

git:

git branch --show-current
# If on protected branch, create feature branch:
git checkout -b "feature/issue-<number>-<description>"
git fetch origin

Implementation Standards

Write failing tests first capturing acceptance criteria
Implement minimal code to make tests pass
Refactor while maintaining green tests
Follow project patterns from CLAUDE.md
Add meaningful comments for complex logic
Update docs if public APIs change

Push and PR

jj:

jj squash -m "feat: final commit message"
jj bookmark set <branch> -r @
jj git push --bookmark <branch>

git:

git push -u origin HEAD

PR creation:

gh pr create --title "[Issue #<number>] Title" --body "$(cat <<'EOF'
## Summary
<bullets>

## Test plan
- [ ] Tests pass
- [ ] Manual verification
EOF
)"

Command Reference

# GitHub
gh issue view <number> --json title,body,labels,assignees,milestone
gh pr create --title "title" --body "body"

# Linear
linear-cli issues
linear-cli issue <team-id>