---
name: issue-resolution
description: Use when picking up, resolving, addressing, fixing, working, tackling, triaging, or closing out one or more GitHub issues (tickets, bug reports, feature requests) in chelis or a shell repo, whether referenced by number (#N) or URL or handed as a batch, and even when a PR already exists. Claims each issue via assignee (gh issue edit --add-assignee @me) before branching or writing any code so others can see it is in progress, scopes the work from the full issue thread (body and every comment), and links the PR with honest Closes/Part-of wording.
title: issue-resolution
canonical_url: https://skilld.dev/gh/chelis-lang/chelis/issue-resolution
last_updated: 2026-10-07T14:45:40.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install chelis-lang/chelis/issue-resolution`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/issue-resolution`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/chelis-lang/chelis/issue-resolution) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/issue-resolution`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/issue-resolution --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/issue-resolution --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Issue Resolution

Use this skill whenever a session or subagent picks up, resolves,
addresses, fixes, works, tackles, or closes out one or more GitHub
issues (tickets, bug reports, feature requests) in chelis or a shell
repo, whether given an issue number, a URL, or a batch to work through,
and even when a PR for the issue already exists.

## Claim The Issue First

- Before writing any code, check the claim state:
  `gh issue view <N> --repo <owner>/<repo> --json state,title,assignees`
- If the issue is already assigned to someone other than the repo owner
  operating this workstation, stop and surface that instead of starting
  work; a live assignee means someone else may be mid-flight.
- If it is unassigned (or assigned only to the operator), claim it:
  `gh issue edit <N> --repo <owner>/<repo> --add-assignee @me`
  `@me` resolves to the authenticated `gh` account (the workstation
  owner, e.g. `rlronan`), never to an agent identity. The assignment is
  the public "in progress" signal for outside collaborators.
- Claim after deciding to work the issue and before branching or
  editing, so the claim window matches the work window. Multiple agents
  on one workstation share one assignee account; branch names
  (`agent/<N>-<slug>`) disambiguate the parallel efforts internally.
- If `gh issue edit` fails for lack of triage rights (for example an
  upstream repo worked from a shell), leave a claiming comment on the
  issue naming the working branch instead.
- Do not claim a closed issue. If the problem persists at head, file a
  residue issue that links the closed one, then claim the new issue.

## Scope From The Whole Thread

- Read the body and every comment (`gh issue view <N> --comments`)
  before scoping. Late comments often rescope an issue: partial fixes
  already landed, escalations, added reproducers, or narrowed intent.
- Check linked PRs and any expected-to-fail pins the thread names; run
  those pins first to see the live failure mode before changing code.

## Land With Honest Linkage

- Follow the repo contract (`AGENTS.md`) for the change itself:
  spec-first tests, negative-test parity, public-surface sync.
- Automatic issue closure is disabled for this repository: `Closes #N`
  in a PR body or commit message does nothing. Say `Closes #N` only when
  the PR fully resolves the issue, and `Part of #N` plus an explicit
  statement of what remains otherwise. Either way the sentence is a claim
  for the reviewer, not an instruction to GitHub.
- Merging does not close the issue. After the PR merges, close it as a
  separate step once the work is verified (`gh issue close <N>` with a
  comment naming the PR), or leave it open and say what remains.
- Keep the assignee in place while the PR is open; closing the issue
  releases the claim naturally.

## Release Stale Claims

- If the work is abandoned with nothing pushed, remove the assignment
  (`gh issue edit <N> --remove-assignee @me`) or comment with current
  status, so a stale claim does not block others from picking it up.
