graduation-backend

Validate graduation backend changes against handwritten loading rules and baseline tests.

26|1|Updated Jan 8, 2025
One-click install
npx skills add https://github.com/allcll/allcll-backend --skill graduation-backend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graduation-backend
Source: https://github.com/allcll/allcll-backend/tree/main/.agents/skills/graduation-backend
Command: npx skills add https://github.com/allcll/allcll-backend --skill graduation-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps keep graduation-related backend changes aligned with the handwritten rules used to load and interpret course catalog data, preventing the code from silently missing important edge cases.

Core Features & Use Cases

  • Rule-safe backend changes: Use it when editing graduation domain code so resolver-layer logic, data-source precedence, and baseline checks are preserved.
  • Knowledge and data validation: Apply it to verify upstream knowledge files and imported schedule data before relying on them in runtime behavior.
  • Regression prevention: Use it during refactors or bug fixes to ensure existing ingestion and grading assumptions remain enforced.

Quick Start

Apply the graduation-backend skill when updating graduation, sheet support, or admin graduation code so the AI checks rule sources, resolver flow, and baseline test impact before making changes.

Frequently Asked Questions about graduation-backend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce handwritten loading rules during graduation backend refactoring?

To enforce handwritten loading rules during graduation backend refactoring, apply rule-safe checks to verify resolver-layer logic, data-source precedence, and baseline tests before modifying ingestion or resolver flow code.

Why does my graduation domain code silently miss course catalog edge cases?

Graduation domain code misses edge cases when changes bypass handwritten rules for loading course catalog data, requiring prechecks on rule sources and knowledge validation to prevent inconsistent data handling.

What is the best way to prevent regression when updating resolver flow logic?

The best way to prevent regression in resolver flow logic is to gate changes on knowledge validation and baseline tests, ensuring existing ingestion and grading assumptions remain enforced during refactors or bug fixes.

Does this approach work for admin graduation changes and support sheet updates?

Yes, this validation approach works for admin graduation changes and support sheet updates by enforcing resolver-layer access and prechecking rule sources across ingestion, resolver flow, and regression-sensitive refactors.

How do I validate upstream knowledge files before relying on them in runtime behavior?

Validate upstream knowledge files by applying data validation checks to imported schedule data and rule sources before runtime execution, ensuring graduation backend code aligns with handwritten loading rules and grading assumptions.