Index of every page on this site: llms.txt
All skills
chelis-lang avatar

/issue-resolution

@f7af876
Run it yourself

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.

  • 1 file
  • 3.5 KB
  • Updated 3 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/chelis-lang/chelis/issue-resolution

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈142 tokens for metadata: the name and description. ≈760 when used: this file.

Description uses 7.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈568 characters, or 7.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at f7af876. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 3 months ago

README badge

README badge for chelis-lang/chelis/issue-resolution