All authors
Claude Skills by xiongxianfei
github.com/xiongxianfei75 skills0 installs95 views
- Plans- Status: done - Owner: maintainers - Start date: 2026-04-29 - Last updated: 2026-04-30 - Related issue or PR: PR #23 - Supersedes: none - broad_smoke_required: true - broad_smoke_reason: Planned initiative touches governance, public README ownership, canonical skills, generated Codex skill mirrors, generated public adapter packages, lifecycle-managed artifacts, and proposal workflow guidance.Votes: 0GitHub stars: 3
- ProposalsRigorLoop has a clear workflow contract, a public README, and a growing set of lifecycle skills, but it does not yet have a compact canonical vision document that answers what the project is, who it is for, what it refuses to become, and how future proposals should be checked for fit.Votes: 0GitHub stars: 3
- ProposalsThe `learn` skill is now correctly classified as periodic or explicitly invoked, but its final artifact model is still deferred. The current guidance says scheduled follow-ups and no-learn rationales use temporary contributor-visible or review-visible surfaces until a focused learn refactor defines the final model.Votes: 0GitHub stars: 3
- BugfixDiagnose or fix unexpected behavior, failing evidence, incidents, regressions, and bug reports with bounded authority and identity-stable proof.Votes: 0GitHub stars: 3
- Ci MaintenanceAuthor or review repository-owned CI workflows, validation automation, and related configuration when coverage, speed, caching, permissions, triggers, or ordinary hardening needs maintenance.Votes: 0GitHub stars: 3
- Code ReviewIndependently assess the complete delivered Change, or provide explicitly requested interim advice. One whole-change gate precedes final Verify; corrections are reassessed within that gate.Votes: 0GitHub stars: 3
- ConstitutionCreate or update the repository's governing AI-development principles. Use when starting a project, adopting this skill pack, onboarding a brownfield codebase, or when recurring mistakes show that project rules are unclear.Votes: 0GitHub stars: 3
- Delivery ReviewIndependently assess whether a delivery plan can implement the accepted requirements/design and demonstrate the outcome, including dependencies, proof allocation and recovery.Votes: 0GitHub stars: 3
- Design ReviewIndependently assess System Design and Architecture Design together against the accepted requirement basis, including Functions, allocation, Interfaces, ARs and realization.Votes: 0GitHub stars: 3
- ExploreExpand a materially unclear problem or solution space into distinct directions before its decision owner commits. Use when framing, user value, scope, reversibility, or available options are unsettled; use research instead when the options are known and an uncertain fact is the blocker.Votes: 0GitHub stars: 3
- ImplementRealize accepted requirements and reviewed design in authorized, testable milestones. Maintain current evidence and hand off the complete implementation for independent whole-change Code Review.Votes: 0GitHub stars: 3
- LearnCapture durable lessons after implementation, review, verification, or incidents. Use when recurring mistakes, systemic gaps, or explicit retrospective work should guide future contributors.Votes: 0GitHub stars: 3
- PlanTurn accepted requirements and reviewed System/Architecture Design into a proportionate delivery plan with milestones, dependencies, proof and recovery. Use before multi-component or risky implementation.Votes: 0GitHub stars: 3
- PrPrepare or submit a pull request from the actual delivered diff, current review and verification evidence, and explicit external-action authority. Use after final Verify or for an isolated PR preparation request.Votes: 0GitHub stars: 3
- Project MapBuild, refresh, or audit a current-state repository orientation map. Use when architecture, module boundaries, runtime flow, data flow, test layout, CI, ownership, or change placement is unclear. This skill records observed repository structure and bounded inferences; it does not invent future architecture or act as a backlog.Votes: 0GitHub stars: 3
- ResearchReduce a bounded, decision-relevant factual uncertainty with attributable evidence and explicit confidence. Use when platform behavior, compatibility, standards, policies, prices, performance, security, scale, or operational facts could materially change a known decision; use explore instead when the option space itself is unclear.Votes: 0GitHub stars: 3
- VerifyAssess whether current engineering work, applicable reviews and actual evidence justify a scoped result or final completion. Keep Verify separate from authoring and whole-change Code Review.Votes: 0GitHub stars: 3
- VisionProduce or update the project vision and matching README front-matter at project genesis or when current vision no longer reflects the project. This skill is upstream of the per-change workflow.Votes: 0GitHub stars: 3
- Agents OpenaiThis skill depends on Codex agent config.Votes: 0GitHub stars: 3
- Codex Dollar SkillThis skill depends on dollar-prefixed Codex skill invocation.Votes: 0GitHub stars: 3
- Codex Install OnlyThis skill documents only the Codex install location.Votes: 0GitHub stars: 3
- Codex Install With AlternativesThis skill documents Codex and generated adapter install locations.Votes: 0GitHub stars: 3
- Codex InvocationThis skill requires Codex invocation wording.Votes: 0GitHub stars: 3
- Codex Tool AssumptionThis skill assumes Codex runtime controls.Votes: 0GitHub stars: 3
- Generic Artifact PathsThis skill uses generic RigorLoop artifact paths.Votes: 0GitHub stars: 3
- Invalid BodyThis skill has valid metadata but invalid Markdown instruction content.Votes: 0GitHub stars: 3
- Invalid DescriptionThis fixture fails portable description validation.Votes: 0GitHub stars: 3
- Invalid NameThis skill has an invalid portable name.Votes: 0GitHub stars: 3
- Partial PortabilityThis skill is compatible with Codex and Claude Code, but not opencode.Votes: 0GitHub stars: 3
- Portable BasicUse generic RigorLoop artifacts without tool-specific assumptions.Votes: 0GitHub stars: 3
- Portable With AssetsUse a packaged asset while remaining portable across adapter roots.Votes: 0GitHub stars: 3
- Transformable FrontmatterThis skill has Codex frontmatter that can be removed for other adapters.Votes: 0GitHub stars: 3
- Unsupported FrontmatterThis skill has unsupported metadata for non-Codex adapters.Votes: 0GitHub stars: 3
- ProposalUse this fixture when validating generated output asset presence.Votes: 0GitHub stars: 3
- FirstFirst duplicate-name fixture entry.Votes: 0GitHub stars: 3
- SecondSecond duplicate-name fixture entry.Votes: 0GitHub stars: 3
- Missing DescriptionThis fixture is invalid because its frontmatter omits `description`.Votes: 0GitHub stars: 3
- Missing Expected OutputInvalid fixture skill missing the required Expected output section.Votes: 0GitHub stars: 3
- Missing NameInvalid fixture skill missing the required name field.Votes: 0GitHub stars: 3
- Valid SiblingValid sibling skill used to prove the validator still catches a neighboring missing SKILL.md.Votes: 0GitHub stars: 3
- Missing TitleInvalid fixture skill missing the required top-level title.Votes: 0GitHub stars: 3
- Placeholder TextInvalid fixture skill that still contains placeholder text.Votes: 0GitHub stars: 3
- ValidBuild, refresh, or audit a current-state repository orientation map with cited evidence, bounded inference, known gaps, and durable root or area scope.Votes: 0GitHub stars: 3
- Description Too LongUse this skill when the description intentionally exceeds the published skill design contract limit so the validator can prove the portable routing source remains bounded for adapter listings. This sentence is repeated to make the fixture longer than the one thousand twenty four character cap while still looking like ordinary routing prose. Use this skill when the description intentionally exceeds the published skill design contract limit so the validator can prove the portable routing source...Votes: 0GitHub stars: 3
- Plan Assets Fingerprint MismatchUse this fixture when validating structural fingerprint drift.Votes: 0GitHub stars: 3
- Plan Assets Missing Approved AssetUse this fixture when validating exact plan asset inventory.Votes: 0GitHub stars: 3
- Plan Assets Missing FieldsUse this fixture when validating fields-to-fill requirements.Votes: 0GitHub stars: 3
- Plan Assets Missing MetadataUse this fixture when validating asset metadata.Votes: 0GitHub stars: 3
- Plan Assets Missing PlaceholderUse this fixture when validating placeholder requirements.Votes: 0GitHub stars: 3
- Plan Assets Missing Resource Map EntryUse this fixture for the plan asset pilot missing resource-map entry check.Votes: 0GitHub stars: 3