issue-relevance-check

Slash command to evaluate whether an issue or pull request is still relevant, actionable, and worth keeping open

Repository: arisng/github-copilot-fc
Last source activity: June 17, 2026 at 14:06
Detected SKILL.md language: English
Stars: 5
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/arisng/github-copilot-fc --skill issue-relevance-check

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

name	issue-relevance-check
description	Slash command to evaluate whether an issue or pull request is still relevant, actionable, and worth keeping open
metadata	{"author":"arisng","version":"0.1.0"}

Issue Relevance Check

A slash command (/issue-relevance-check) that evaluates whether an issue or pull request is still relevant to the project's current codebase, state, and priorities.

Usage

Trigger the skill by commenting /issue-relevance-check on any issue or pull request in a repository where this skill is installed.

Workflow

Gather context — reads the full issue/PR, checks current codebase state, reviews recent commits/PRs, and searches for duplicates.
Evaluate relevance — assesses applicability, resolution status, superseding items, staleness, and actionability.
Post analysis — returns a structured comment with verdict, evidence, and recommendation.

See references/evaluation-guide.md for the complete evaluation framework and criteria.

Back to search Back to installation

machina-driving

Drive a Machina state machine to a deterministic outcome on behalf of an AI agent. USE WHEN: a task is governed by a state machine (a machine definition JSON with states, transitions, guards, actions, tools, checks, scenarios); executing a workflow that must be deterministic and auditable; running a skill whose SKILL.md declares a `machina:` machine; firing events, checking status, satisfying evidence checks, verifying run integrity with `check`, or producing a terminal report for a machine-driven run; escalating a STUCK run to a human conductor. DO NOT USE FOR: authoring or scoring machine definitions (use machina-authoring); modifying the Machina simulator app or its engine (use machina-simulator); implementing or modifying the driver/runtime tooling such as `scripts/machine-driver.py` (engine development) unless you are a maintainer of this skill upgrading the driver itself; general diagramming or XState/SCXML authoring.

2026-09-09

machina-authoring

Author valid, high-scoring state machines in Machina machine JSON format (spec v3.0.0 / v2.0.0 / v1.0.0). USE WHEN: writing or generating a machine definition (states, transitions, guards, actions, context, scenarios); modeling a real workflow (order fulfillment, refunds, signup, retries) as a Machina state machine; fixing or upgrading a machine JSON for validation or higher compliance score; explaining validation failures or low scores; running the bundled machina-validator.py CLI to validate, score, or generate gaps/scenarios; adding retry guards or cycle protection; or preparing machines for the compliance scorer ("Excellent" ≥90). DO NOT USE FOR: modifying the Machina simulator app, its engine, UI, or SPEC_REGISTRY (use machina-simulator-maintenance), debugging machine-validator.py scripts, XState config authoring, SCXML documents, or general diagramming.

2026-09-08

copilot-cli-subsession

Spawn a new isolated Copilot CLI sub-session from a main Copilot CLI or VS Code session. Use when you need to programmatically create, resume, or chain Copilot CLI sessions with explicit control over session ID, custom agent, model, BYOK provider profile, permissions, and working directory. Triggers: "invoke copilot", "spawn copilot", "copilot sub-session", "programmatic copilot cli", "programmatic copilot subprocess", "copilot cli session id", "resume copilot session", "chain copilot sessions", "isolated copilot session", "subagent copilot cli", "task copilot cli".

2026-09-07

View all from this repository

name	issue-relevance-check
description	Slash command to evaluate whether an issue or pull request is still relevant, actionable, and worth keeping open
metadata	{"author":"arisng","version":"0.1.0"}

Issue Relevance Check

A slash command (/issue-relevance-check) that evaluates whether an issue or pull request is still relevant to the project's current codebase, state, and priorities.

Usage

Trigger the skill by commenting /issue-relevance-check on any issue or pull request in a repository where this skill is installed.

Workflow

Gather context — reads the full issue/PR, checks current codebase state, reviews recent commits/PRs, and searches for duplicates.
Evaluate relevance — assesses applicability, resolution status, superseding items, staleness, and actionability.
Post analysis — returns a structured comment with verdict, evidence, and recommendation.

See references/evaluation-guide.md for the complete evaluation framework and criteria.

issue-relevance-check

Source facts

Install options

Review the source files

Issue Relevance Check

Usage

Workflow

More from this repository

Issue Relevance Check

Usage

Workflow

More from this repository