All authors
Claude Skills by rumoii
github.com/rumoii39 skills0 installs0 views
- Gradersrumo-clarify is invoked.Votes: 0GitHub stars: 3
- Gradersrumo-coding-guidelines is invoked.Votes: 0GitHub stars: 3
- Gradersrumo-database-change-safety is invoked.Votes: 0GitHub stars: 3
- Gradersrumo-debug is invoked.Votes: 0GitHub stars: 3
- Gradersrumo-filesystem-safety is invoked.Votes: 0GitHub stars: 3
- Gradersrumo-frontend is invoked.Votes: 0GitHub stars: 3
- Gradersrumo-interface is invoked.Votes: 0GitHub stars: 3
- Gradersrumo-lifecycle-safety is invoked.Votes: 0GitHub stars: 3
- GradersNo rumo skill is invoked.Votes: 0GitHub stars: 3
- Gradersrumo-plan is invoked.Votes: 0GitHub stars: 3
- Gradersrumo-git-commit is invoked.Votes: 0GitHub stars: 3
- Gradersrumo-prose is invoked.Votes: 0GitHub stars: 3
- Gradersrumo-remote-ops is invoked.Votes: 0GitHub stars: 3
- Gradersrumo-review is invoked.Votes: 0GitHub stars: 3
- Gradersrumo-test is invoked.Votes: 0GitHub stars: 3
- Gradersrumo-verify is invoked.Votes: 0GitHub stars: 3
- Rumo Daily ReportGenerate a plain-language Chinese daily report from the current completed conversation and append it to the configured date-based TXT file when the user asks to整理日报 or generate a daily report.Votes: 0GitHub stars: 3
- Rumo DiagramUse when creating, revising, previewing, exporting, or validating engineering diagrams, either Mermaid flowcharts and business process diagrams (流程图、业务链路图、校验/审核分支图) as Markdown + HTML preview + PNG, or architecture, deployment, security-zone, interface, and network topology diagrams built from a confirmed fact model. Do not use for screenshots, photos, or general image generation.Votes: 0GitHub stars: 3
- Rumo Document WritingUse when drafting, revising, splitting, formatting, or quality-checking formal Word delivery documents such as designs, reviews, tests, acceptance materials, deployment manuals, operations manuals, interface documents, and technical reports. Do not use for repository Markdown, code comments, or other in-repo prose; use rumo-prose instead.Votes: 0GitHub stars: 3
- Rumo ImagegenGenerate and save one raster image through a user-configured OpenAI-compatible image endpoint. Use only when the user explicitly selects this configured service; do not use for diagrams, screenshots, or when a first-party image tool is more appropriate.Votes: 0GitHub stars: 3
- Rumo Linux InspectUse when explicitly asked for a read-only Linux inspection, either a hardware inventory that saves raw evidence and a concise Chinese device-configuration TXT, or a memory and performance inspection for high memory, OOM, garbage-collection, slow-log, process, or port symptoms. Never change the target, install packages, or operate services.Votes: 0GitHub stars: 3
- Rumo Offline Delivery AuditUse when building, reviewing, or accepting an offline delivery package, deployment archive, image bundle, or field-installation kit. Verify artifact integrity, dependency closure, source provenance, installer and rollback behavior, embedded documentation, and the exact distinction between source checks, package checks, isolated installation, and real target acceptance. Do not use for bounded online deployment to an existing environment.Votes: 0GitHub stars: 3
- Rumo ClarifyUse before implementing a request whose goal, scope, acceptance criteria, or a risky decision is still unclear, such as a vague feature ask, an open-ended change, or a task touching data, permissions, deletion, or external publication without a stated target. Group the questions that can be answered now, with recommendations; follow up only for newly exposed consequential decisions, or explore deeper when the user asks. Do not use when the request is already specific, for pure questions, or f...Votes: 0GitHub stars: 3
- Rumo Coding GuidelinesUse when writing, fixing, or refactoring code in a software repository, as the baseline discipline alongside more specific skills. Ground every edit in the real code path, do only the requested work and what it necessarily implies, avoid speculative abstraction and drive-by edits, and close with verification. Do not use alone for review-only, diagnosis-only, or question-answering requests.Votes: 0GitHub stars: 3
- Rumo Database Change SafetyUse when planning, reviewing, generating, testing, or executing any write to an application database, including schema migrations, new columns, backfills, data repairs, cleanup, resets, destructive SQL, restores, and rollback. Start read-only, identify the exact database and application versions, require explicit authorization before changing any existing or persistent database, and prove backup, compatibility, bounded effects, and rollback readiness. Use rumo-debug instead for purely read-on...Votes: 0GitHub stars: 3
- Rumo DebugUse when investigating a software defect, failing test, flaky behavior, remote-environment anomaly, or unexplained UI or API behavior. Reproduce, localize, and prove the cause with an evidence chain across source, runtime, data, middleware, deployment, and client boundaries; stay read-only unless the request also asks for the fix. Do not use for planned database writes or for reviewing a diff.Votes: 0GitHub stars: 3
- Rumo Filesystem SafetyUse when about to delete or bulk-clean files or directories: recursive or wildcard removal, git clean or reset --hard that discards working-tree content, purging build outputs or caches, or deleting untracked or ignored content. Scales the review to the blast radius. Do not use for writing a cleanup script that is not run now, for database data cleanup (use rumo-database-change-safety), or for source-file removal within a requested refactor.Votes: 0GitHub stars: 3
- Rumo FrontendUse when building, refactoring, or designing frontend pages and components, including a new interface with no existing pattern to follow or a request to improve visual quality or accessibility; starting or troubleshooting a local frontend development server (package scripts, backend proxy, ports, certificates, micro-frontends); or capturing browser evidence such as screenshots or a short GIF when explicitly asked. Do not capture persistent visual evidence merely because frontend code changed.Votes: 0GitHub stars: 3
- Rumo Git CommitUse when the user explicitly asks to commit, tag, release, push, clean up history, land a worktree or feature branch, or open or update a pull request. Follow repository conventions for branch selection, commit language, message format, verification, and release versioning. Do not use merely because work is finished; without an explicit request, stop after rumo-verify.Votes: 0GitHub stars: 3
- Rumo HandoffUse when the user asks to hand off, hand over, pause, or package the current task so another session, agent, or client can continue it. Write a self-contained handoff document with goal, decisions, repository state, verified and unverified results, next steps, and how to resume. Do not use for ordinary progress updates or end-of-task summaries.Votes: 0GitHub stars: 3
- Rumo InterfaceUse when adding, changing, deprecating, or reviewing anything another process, version, or product reads or writes, such as an HTTP/JSON endpoint or OpenAPI contract, DTO, event or queue message, protocol, configuration field, database representation, persisted file, or export. Trace every producer and consumer, define old/new compatibility and rollout order, and for HTTP routes also cover authentication, authorization, idempotency, rate limits, pagination, and response cost. Do not use for p...Votes: 0GitHub stars: 3
- Rumo Lifecycle SafetyUse when implementing, fixing, or reviewing asynchronous or long-lived behavior involving background tasks, thread pools, scheduled jobs, message-queue consumers such as Kafka, terminal sessions, subprocesses, retries, cancellation, timeouts, shutdown, or resource cleanup. Establish explicit ownership and state transitions, make retry and disposal safe, and verify failure and restart paths instead of only the successful call.Votes: 0GitHub stars: 3
- Rumo PlanUse when turning an agreed multi-step or cross-module task into a short spec and verifiable task breakdown before implementation, when executing an agreed plan task by task, or when creating, updating, superseding, implementing, or rejecting a durable engineering decision record (ADR) for a cross-module contract, data or wire format, permission model or security policy, lifecycle rule, deployment topology, migration, or rollback strategy. Do not use for single-file fixes or mechanical edits, ...Votes: 0GitHub stars: 3
- Rumo Project ProfileResolve and validate optional private project profiles for other Rumo skills. Use when a workflow needs project-specific repository, frontend, backend, runtime, data, document, or credential configuration that the current repository does not provide, or when creating or checking a profile. Do not use for ordinary repository discovery.Votes: 0GitHub stars: 3
- Rumo ProseUse when writing, reviewing, or trimming prose in a software repository, including Markdown, code and test comments, JavaDoc/JSDoc, diagnostics, logs, API errors, configuration descriptions, UI strings, prompts, and agent-facing files such as SKILL.md, AGENTS.md, and CLAUDE.md. Keep every behavior and failure fact while removing repetition, narration, and session residue. Do not use for formal Word delivery documents.Votes: 0GitHub stars: 3
- Rumo Remote OpsUse when querying or changing a remote Linux host over SSH, installing, configuring, upgrading, or removing a systemd or Docker Compose service, planning or performing host configuration or service-data backups and restores, or planning a bounded deployment of selected application artifacts to an existing development or test environment from a project profile. Verify target and authorization, protect access, prepare recovery before changes, and reconcile uncertain execution before retrying. D...Votes: 0GitHub stars: 3
- Rumo ReviewUse for a read-only code review of uncommitted changes, a branch diff, or a commit, or a named-scope audit of existing issues; for an explicitly requested review-fix-repeat loop until no blocking findings remain; for an explicitly requested simplification audit of removable complexity; or for addressing review feedback from someone else. Report correctness, security, lifecycle, compatibility, operations, and test risks with file-and-line evidence. Do not use to run pre-handoff checks; use rum...Votes: 0GitHub stars: 3
- Rumo TestUse when planning, writing, or assessing tests for a behavior change, including whether existing tests are enough, which evidence layers (unit, integration, browser, artifact, deployment, field) to use, and test-driven development. Also use unprompted when implementing a change that touches money, auth, durable data, concurrency, migrations, public interfaces, or irreversible effects, to rate its risk and enter high-assurance spec-and-evidence mode when it is high. Do not use to find the root...Votes: 0GitHub stars: 3
- Rumo VerifyUse before claiming work is done, marking it ready, committing for handoff, or pushing, and when asked to verify a change; establish the exact committed and dirty change scope, run the smallest sufficient checks, and report only commands actually run. Also use when adding, changing, reviewing, or diagnosing a repository-owned CI check, static verifier, generated-file check, pre-commit rule, or aggregate test entry point. Never commits, pushes, deploys, or changes remote systems; do not use fo...Votes: 0GitHub stars: 3