Start Issue

What it does

When your agent uses it

• Beginning work on any new issue: start issue 20408
• /start-issue 20408
• Prepare env for issue 20408

Example prompts

• “start issue 20408”
• “/start-issue 20408”
• “prepare env for issue 20408”
• “/start-issue”

Requirements

• Pre-approved tools (allowed-tools): Bash, Read, Edit, Grep

Workflow steps

6 steps, taken from the step headings in SKILL.md.

1. 1Fetch Issue Title
2. 2Create Feature Branch from development
3. 3Set persistence.xml to Local JNDI
4. 4Assign Issue on GitHub
5. 5Project Board (CareCode: HMIS Board)
6. 6Summary

What it can do on your machine

Read from SKILL.md and the folder at commit d5d2020. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Bash
  • Read
  • Edit
  • Grep

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • gh
  • git

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • github.com

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Start Issue loads about 1.5k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 559 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~85

When it runs · the whole SKILL.md, loaded when a task matches

~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NotePre-approves every shell command (allowed-tools: Bash)SKILL.md

  allowed-tools: Bash, Read, Edit, Grep

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hmislk/hmis at commit d5d2020, republished under its GPL-3.0 licence (© hmislk). 559 words, ~1,493 tokens.

name

start-issue

description

Full environment setup when starting work on a GitHub issue. Creates a feature branch from origin/development, swaps persistence.xml to local JNDI settings, assigns the issue, and guides project board setup. Use when beginning work on any new issue: "start issue 20408", "/start-issue 20408", or "prepare env for issue 20408".

allowed-tools

Bash, Read, Edit, Grep

disable-model-invocation

false

argument-hint

<issue-number> [short-description] [local-jndi-name]

gh issue view $0 --repo hmislk/hmis --json title,body --jq '.title'

git fetch origin
git checkout -b $0-<description> origin/development
git push -u origin $0-<description>

gh issue edit $0 --repo hmislk/hmis --add-assignee buddhika75

! gh auth refresh -s project

# 1. Issue node ID
ISSUE_NODE=$(gh api repos/hmislk/hmis/issues/$0 --jq '.node_id')

# 2. Add to project #11, or get the existing item, and capture the item ID
ITEM_ID=$(gh api graphql -f query='
mutation($p:ID!,$c:ID!){ addProjectV2ItemById(input:{projectId:$p,contentId:$c}){ item{ id } } }' \
  -f p=PVT_kwDOAHw-zs4ApMln -f c="$ISSUE_NODE" --jq '.data.addProjectV2ItemById.item.id')

# 3. Set Status = In Progress
gh api graphql -f query='
mutation($p:ID!,$i:ID!){ updateProjectV2ItemFieldValue(input:{
  projectId:$p, itemId:$i,
  fieldId:"PVTSSF_lADOAHw-zs4ApMlnzggpN3k",
  value:{singleSelectOptionId:"47fc9ee4"} }){ projectV2Item{ id } } }' \
  -f p=PVT_kwDOAHw-zs4ApMln -f i="$ITEM_ID"

# 4. READ BACK: this output is the only thing that may be reported as the board status
gh api graphql -f query='
query($i:ID!){ node(id:$i){ ... on ProjectV2Item{
  fieldValueByName(name:"Status"){ ... on ProjectV2ItemFieldSingleSelectValue{ name updatedAt } } } } }' \
  -f i="$ITEM_ID" --jq '.data.node.fieldValueByName'

© hmislk, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/start-issue of hmislk/hmis.

Open the folder on GitHubat commit d5d2020