agentleFS
Vernum-ProjectenVernum-Projecten/cc-shift/.claude/skills/phase-status/SKILL.md

phase-status

Skill2 starsChanged 29 days agoApache-2.0View on GitHub

Prints the tracker's open issues (pinned first, with native relationships), the in-flight issue's unchecked acceptance criteria, and a short git status. Use when the user asks "where are we", "what's in flight", or at the start of a work session to orient.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the user asks for the board view, scripts/gh/project.sh board prints the roadmap board grouped by Status, a presentation view over the …

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/phase-status

A fast orientation dump, the orient step of the issue workflow (.claude/rules/issue-workflow.md). Read-only; it makes no changes. The live state below is injected at invocation time; ground the answer in it rather than in stale conversation memory.

Live state (injected)

The tracker: open GitHub issues (with native relationships)

Each line carries <Type/Priority> (the native issue type and the Priority field, ? where unset), {k/n} sub-issue progress, child-of #parent, and open BLOCKED-by/blocks edges (.claude/rules/issue-relationships.md).

gh api graphql -f query='query($owner: String!, $name: String!) { repository(owner: $owner, name: $name) { issues(first: 100, states: OPEN, orderBy: {field: CREATED_AT, direction: DESC}) { nodes { number title issueType { name } issueFieldValues(first: 10) { nodes { ... on IssueFieldSingleSelectValue { field { ... on IssueFieldSingleSelect { name } } value } } } labels(first: 20) { nodes { name } } milestone { title } parent { number } subIssuesSummary { total completed } blockedBy(first: 30) { nodes { number state } } blocking(first: 30) { nodes { number state } } } } } }' -f owner="$(gh repo view --json owner --jq .owner.login)" -f name="$(gh repo view --json name --jq .name)" --jq '.data.repository.issues.nodes[] | ((.issueType.name // "?") + "/" + ([.issueFieldValues.nodes[] | select(.field.name == "Priority") | .value] | first // "?")) as $tp | ([.labels.nodes[].name] | join(", ")) as $labels | ([.blockedBy.nodes[] | select(.state == "OPEN") | "#\(.number)"]) as $b | ([.blocking.nodes[] | select(.state == "OPEN") | "#\(.number)"]) as $k | "#\(.number)  \(.title)  <\($tp)>  [\($labels)]" + (if .milestone then "  (\(.milestone.title))" else "" end) + (if .parent then "  child-of #\(.parent.number)" else "" end) + (if .subIssuesSummary.total > 0 then "  {\(.subIssuesSummary.completed)/\(.subIssuesSummary.total)}" else "" end) + (if ($b | length) > 0 then "  BLOCKED-by \($b | join(","))" else "" end) + (if ($k | length) > 0 then "  blocks \($k | join(","))" else "" end)'

Git

cd "${CLAUDE_PROJECT_DIR}" && git status --short | head -40 && echo "---" && git log --oneline -5

Steps

  1. Summarize the tracker state: which issue is the current focus (pinned, milestone-assigned, or the one the branch implements) and what its stated next action is. For the in-flight issue, run gh issue view <n> --json title,body,comments --jq '.title, .body, (.comments[] | "--- comment ---", .body)' (--comments prints nothing for an issue without comments, issue-workflow.md §The loop) and report the latest status comment and the unchecked ## Acceptance criteria boxes, plus scripts/gh/rel.sh tree <n> for its parent, children, and blockers. Flag any open issue shown BLOCKED-by an open blocker: it is stuck until the blocker closes and is not a pickup candidate (.claude/rules/issue-relationships.md). Flag any open issue shown <?/?> or with a ? half: it lacks its type or priority (it was filed without them), and scripts/gh/fields.sh sets them.
  2. Summarize the git state from the injected output: current branch work, uncommitted files, last commits. Flag uncommitted work that looks finished; never leave finished work sitting unmerged. Flag an open pull request without auto-merge armed (gh pr list --json number,autoMergeRequest).
  3. If the user asks for the board view, scripts/gh/project.sh board prints the roadmap board grouped by Status, a presentation view over the same issues rather than a second source of truth (.claude/rules/project-board.md); the issue list above stays the working ground truth. Flag any In Progress item nobody is working on (it should be parked back to todo). If the board does not exist yet, the command fails loud; note that and continue.
  4. Do not modify any issue or make any commit; this is a read-only status check. If the user wants the next task turned into a work plan, point them at /next-task instead.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.