Run any Skill in Manus with one click

specrail-install

Stars22

Forks0

UpdatedJuly 1, 2026 at 02:58

Use when installing, updating, verifying, or adopting SpecRail for agents. Guides local Codex skill installation, global AGENTS.md guidance setup, repository adoption planning, dry-run-first verification, and explicit human authorization boundaries.

Installation

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.

Run Skill in Manus

Source

majiayu000

majiayu000/specrail

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name	specrail-install
description	Use when installing, updating, verifying, or adopting SpecRail for agents. Guides local Codex skill installation, global AGENTS.md guidance setup, repository adoption planning, dry-run-first verification, and explicit human authorization boundaries.

SpecRail Install

Use this skill for agent-facing SpecRail setup. The skill is the entrypoint; CLI tools are deterministic helpers the agent runs after selecting the setup route.

Routes

doctor: inspect current setup without writing files.
install_local_skills: install or update local Codex skills.
install_global_guidance: add or update global agent guidance.
adopt_repo: plan or perform SpecRail pack adoption in a target repository.

Steps

Identify the route from the user's request. If the user only asks whether SpecRail is installed, choose doctor.
Read the active repo instructions and AGENT_USAGE.md.
Run dry-run checks before any write:

python3 tools/install_codex_skills.py --repo .
python3 checks/check_workflow.py --repo .

For install_local_skills, use --apply only when the user explicitly asks to install or update local Codex skills:

python3 tools/install_codex_skills.py --repo . --apply

For install_global_guidance, update ~/.codex/AGENTS.md only after an explicit user request. Use a small managed SpecRail section or update the existing SpecRail section; do not rewrite unrelated global instructions.
For adopt_repo, first report the target repo, files to copy, files that would be preserved, and validation commands. Do not copy pack files into a target repo unless the user explicitly asks.
Verify after writes:

python3 checks/check_workflow.py --repo .
python3 -m pytest -q

When local skills were installed, also verify installed SKILL.md hashes match skills-lock.json.

Boundaries

Dry-run is the default.
Do not install local skills, modify global AGENTS.md, copy pack files into a repo, create remote issues or PRs, add labels, approve, merge, or bypass maintainers unless the user explicitly asks for that action.
Keep repo adoption separate from local agent setup.
Report which layer changed: local skills, global guidance, target repo pack, or none.

More from this repository

same repository

specrail-plan-tasks

majiayu000/specrail

Use when turning an approved SpecRail product and technical spec into the numbered `tasks.md` plan. Creates stable task IDs, owners, done-when conditions, verification commands, dependencies, and handoff notes without implementing the tasks.

2026-07-1122

specrail-write-product-spec

majiayu000/specrail

Use when writing or updating a SpecRail product spec for a linked issue. Produces the numbered `product.md` spec from the locale-appropriate template, focusing on user-facing behavior, goals, non-goals, and acceptance criteria without implementation detail.

2026-07-1122

specrail-write-tech-spec

majiayu000/specrail

Use when writing or updating a SpecRail technical spec for a linked issue. Produces the numbered `tech.md` spec from the locale-appropriate template, translating accepted product behavior into design, affected files, risks, verification, and rollback without starting implementation.

2026-07-1122

implx

majiayu000/specrail

Use when the user says "implx", "use implx", "用 implx", or asks for the one-line SpecRail queue shortcut. Plain implx means drain the full actionable issue/PR queue in auto mode: run SpecRail preflight, create missing spec/task PR work before implementation, use threads for reviewer/merge-reviewer lanes when available, create per-issue implementation PRs, require CI/reviewThreads/pr_gate evidence, auto-merge on complete evidence, and perform closure audit. Say "implx review" / "implx 人工" for the review mode that keeps per-PR human merge authorization.

2026-07-0722

specrail-implement-queue

majiayu000/specrail

Use when implementing or draining a GitHub issue/PR queue in a SpecRail-governed repository where approved specs already exist, such as multiple numbered specs/GH packets that need one or more implementation PRs per issue. Maps issues to specs and existing PRs, supports full-queue drain requests from implx, selects single-agent or optional threads orchestration, preserves partial versus final closing semantics, and requires SpecRail verification plus PR gates before merge-readiness claims.

2026-07-0722

specrail-pr-gate

majiayu000/specrail

Use before reporting a SpecRail PR as merge-ready. Collects read-only PR evidence, runs the offline PR gate, checks linked work, current head SHA, CI, review decision, review threads, merge state, and human merge authorization without merging.

2026-07-0422

name	specrail-install
description	Use when installing, updating, verifying, or adopting SpecRail for agents. Guides local Codex skill installation, global AGENTS.md guidance setup, repository adoption planning, dry-run-first verification, and explicit human authorization boundaries.

SpecRail Install

Use this skill for agent-facing SpecRail setup. The skill is the entrypoint; CLI tools are deterministic helpers the agent runs after selecting the setup route.

Routes

doctor: inspect current setup without writing files.
install_local_skills: install or update local Codex skills.
install_global_guidance: add or update global agent guidance.
adopt_repo: plan or perform SpecRail pack adoption in a target repository.

Steps

Identify the route from the user's request. If the user only asks whether SpecRail is installed, choose doctor.
Read the active repo instructions and AGENT_USAGE.md.
Run dry-run checks before any write:

python3 tools/install_codex_skills.py --repo .
python3 checks/check_workflow.py --repo .

For install_local_skills, use --apply only when the user explicitly asks to install or update local Codex skills:

python3 tools/install_codex_skills.py --repo . --apply

For install_global_guidance, update ~/.codex/AGENTS.md only after an explicit user request. Use a small managed SpecRail section or update the existing SpecRail section; do not rewrite unrelated global instructions.
For adopt_repo, first report the target repo, files to copy, files that would be preserved, and validation commands. Do not copy pack files into a target repo unless the user explicitly asks.
Verify after writes:

python3 checks/check_workflow.py --repo .
python3 -m pytest -q

When local skills were installed, also verify installed SKILL.md hashes match skills-lock.json.

Boundaries

Dry-run is the default.
Do not install local skills, modify global AGENTS.md, copy pack files into a repo, create remote issues or PRs, add labels, approve, merge, or bypass maintainers unless the user explicitly asks for that action.
Keep repo adoption separate from local agent setup.
Report which layer changed: local skills, global guidance, target repo pack, or none.