New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Cross-Layer Change Sync Checklist

by ZeroDeng01 in ZeroDeng01/sublinkPro

A checklist for keeping backend, frontend, documentation and skill API reference changes in step, so a change touching several layers lands in one commit or pull request.

MITAuto-check passedDevelopment

Install Cross-Layer Change Sync Checklist

skills CLI
$ npx skills add ZeroDeng01/sublinkPro --skill cross-layer-sync -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ZeroDeng01/sublinkPro cross-layer-sync --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ZeroDeng01/sublinkPro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/cross-layer-sync .claude/skills/cross-layer-sync && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cross-layer-sync
GitHub stars
1.7k
Token cost
~1.9k tokens
SKILL.md length
819 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

A checklist for keeping backend, frontend, documentation and skill API reference changes in step, so a change touching several layers lands in one commit or pull request.

  • Works in 3 steps: Identify which layers your change touches → Read AGENTS.md section 9 "Cross-layer… → Review CONTRIBUTING.md for cross-layer…
  • Changing an API route or payload that the frontend also depends on
  • SKILL.md covers When to use this skill, Core Principle, Prerequisites and Backend → Frontend Sync…, plus 9 more sections
  • Calls yarn and go

What it does

This skill is a checklist rather than an automated tool. Its core rule is that a change must be atomic across layers: when it touches the backend, frontend, docs or the project's skill API reference, every affected layer is updated in the same pull request or commit. It is meant to be invoked by a post-development workflow, not called directly by users.

Before starting, you identify which layers the change touches and read the cross-layer synchronization section of AGENTS.md and CONTRIBUTING.md. The backend-to-frontend list covers API contracts (routes, payloads, response and error handling, TypeScript types), field names and validation, permission checks and route guards, response parsing and state management, task result and notification rendering with i18n keys, and the skill API reference when /api/v1 or /c endpoints change. The frontend-to-backend list verifies that endpoints, payload shapes, authentication needs, accepted field values, validation rules and the database schema still match.

The paths in the checklist refer to one project's layout, such as webs/src/api, webs/src/views and webs/src/i18n/locales, and to its skill-sublinkpro reference files, so the skill fits that repository best.

When your agent uses it

  • Changing an API route or payload that the frontend also depends on
  • Renaming a field or changing its validation across backend and frontend
  • Updating user-facing text or error messages that appear in several places
  • Checking that documentation still matches runtime behavior before opening a pull request

Example prompts

  • “I renamed the subscription field in the backend. Walk me through what the frontend needs to change.”
  • “Run the cross-layer checklist on this branch before I open the pull request.”
  • “Our permission checks changed on the backend; update the route guards and UI visibility to match.”
  • “The /api/v1 endpoints changed. Which docs and reference files need updating?”

Requirements

  • A project with separate backend, frontend and documentation layers

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Identify which layers your change touches
  2. Read AGENTS.md section 9 "Cross-layer synchronization"
  3. Review CONTRIBUTING.md for cross-layer sync requirements

What it can do on your machine

Read from SKILL.md and the folder at commit 11479da. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • yarn
    • go

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use yarn, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cross-Layer Change Sync Checklist loads about 1.9k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 819 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~50
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ZeroDeng01/sublinkPro at commit 11479da, republished under its MIT licence (© ZeroDeng01). 819 words, ~1,902 tokens.

Download SKILL.mdSave it as .claude/skills/cross-layer-sync/SKILL.md (or your agent's skills folder).
name
cross-layer-sync
description
Cross-layer synchronization guide for backend, frontend, and documentation changes. Invoked by post-dev-workflow when changes affect multiple layers. Not for direct user invocation.
version
1.0.0
author
SublinkPro Team
user-invocable
false

Cross-Layer Synchronization Check Skill

Checklist for ensuring all impacted layers are updated together when changes affect multiple parts of the application.

When to use this skill

Use this skill when changes affect:

  • API contracts, routes, request/response structures
  • Frontend-backend data flow
  • Configuration semantics
  • Documentation that reflects runtime behavior
  • User-facing text or error messages
  • Deployment or build processes

Core Principle

Changes must be atomic across layers: When a change affects multiple layers (backend, frontend, docs, skill API reference), all impacted layers must be updated in the same PR/commit.

Prerequisites

Before running this checklist:

  1. Identify which layers your change touches
  2. Read AGENTS.md section 9 "Cross-layer synchronization"
  3. Review CONTRIBUTING.md for cross-layer sync requirements

Backend → Frontend Sync Checklist

When backend changes affect:
API contracts
  • Updated route paths in frontend (webs/src/api/)
  • Updated request payload structures
  • Updated response handling
  • Updated error handling
  • Updated TypeScript types (if applicable)
Fields
  • Updated field names in frontend requests
  • Updated field validation
  • Updated form components (webs/src/views/)
  • Updated display logic
Permissions
  • Updated permission checks in frontend
  • Updated UI visibility logic
  • Updated route guards
Response structures
  • Updated response parsing
  • Updated state management
  • Updated display components
  • Updated loading/error states
Task results or notifications
  • Updated task result rendering
  • Updated notification display
  • Added i18n keys if needed (webs/src/i18n/locales/)
Skill API (if /api/v1/* or /c/* changed)
  • Updated skill-sublinkpro/reference/api.md endpoint documentation
  • Updated skill-sublinkpro/SKILL.md workflow descriptions (if affected)
  • Updated request/response examples
  • Updated error handling examples

Frontend → Backend Sync Checklist

When frontend changes affect:
API dependencies
  • Verified backend endpoint still matches
  • Verified request payload structure
  • Verified authentication requirements
Field semantics
  • Verified backend accepts new field values
  • Verified backend validation rules
  • Verified database schema supports changes
Page flows
  • Verified backend supports new flow sequence
  • Verified state transitions are valid
  • Verified all required data is available
i18n keys
  • Backend provides i18nKey + i18nParams (if Web UI display)
  • Both zh-CN and en-US translations added

Configuration → All Layers Sync Checklist

When configuration changes affect:
Environment variables
  • Updated docs/configuration.md + .zh-CN.md
  • Updated .env.example or config.example.yaml
  • Updated Docker configuration examples
  • Updated deployment documentation (skill-sublinkpro/reference/deploy.md)
  • Updated code that reads the variable
Default values
  • Updated code
  • Updated documentation
  • Updated example files
Config precedence
  • Updated docs/configuration.md
  • Verified new precedence order works correctly

Documentation Sync Checklist

When behavior changes require doc updates:
User-facing features
  • Updated README.md + README.zh-CN.md (if feature overview affected)
  • Updated relevant docs/features/*.md + .zh-CN.md
  • Updated screenshots/examples if needed
Developer workflows
  • Updated docs/development.md + .zh-CN.md
  • Updated CONTRIBUTING.md + .zh-CN.md (if contribution flow affected)
Configuration or deployment
  • Updated docs/configuration.md + .zh-CN.md
  • Updated docs/installation.md + .zh-CN.md
  • Updated skill-sublinkpro/reference/deploy.md
API contracts
  • Updated skill-sublinkpro/reference/api.md
  • Updated API examples and error codes
Documentation map
  • Updated skill-sublinkpro/reference/docs.md if new docs added or paths changed
Bilingual consistency
  • Updated both English and *.zh-CN.md versions
  • Verified language switch links work
  • Verified relative links are consistent

Verification Checklist

Code verification
  • Frontend: Ran yarn run lint (in webs/ directory)
  • Frontend build: Ran yarn run build (if routing, assets, or build affected)
  • Backend format: Ran gofmt -w <changed-files>
  • Backend lint: Ran golangci-lint run
  • Backend tests: Ran relevant go test ./...
Show full SKILL.md (337 more words)Show less
Manual verification
  • Tested the change end-to-end in local environment
  • Verified both light and dark modes (if UI change)
  • Verified desktop and mobile (if UI change)
  • Checked browser console for errors
  • Verified API responses match frontend expectations

When one layer doesn't need changes

If you've checked an impacted layer and confirmed it truly doesn't need changes, document this in your change summary:

Example: "Checked frontend API layer (webs/src/api/subscriptions.js) - no changes needed because new backend field is optional and frontend uses default behavior."

Common Cross-Layer Change Patterns

Adding a new API endpoint
  1. Backend: Add route, handler, validation
  2. Frontend: Add API client function (webs/src/api/)
  3. Frontend: Add UI component/view (webs/src/views/)
  4. i18n: Add translations for UI text
  5. Docs: Update skill-sublinkpro/reference/api.md
  6. Tests: Add backend handler tests
Changing a data model field
  1. Backend: Update model, migration, validation
  2. Backend: Update API handlers
  3. Frontend: Update API calls
  4. Frontend: Update display components
  5. Frontend: Update forms/inputs
  6. Docs: Update feature documentation
Modifying configuration behavior
  1. Backend: Update config parsing
  2. Backend: Update runtime behavior
  3. Docs: Update docs/configuration.md + .zh-CN.md
  4. Docs: Update example configs
  5. Docs: Update skill-sublinkpro/reference/deploy.md
  6. Tests: Add config validation tests

Delivery Requirements

Before marking complete, the change summary must include:

  1. Layers changed: List which layers were modified
  2. Layers checked: List which layers were inspected but didn't need changes
  3. Justification: For unchanged layers, briefly explain why no sync was needed
  4. Verification: List which validation commands were run

Anti-patterns to avoid

  • ❌ Changing backend API without updating frontend
  • ❌ Changing frontend behavior without verifying backend support
  • ❌ Updating code without updating documentation
  • ❌ Updating only English docs without Chinese versions
  • ❌ Claiming "no sync needed" without actually checking

Exit criteria

✅ Can exit when:

  • All impacted layers are synchronized
  • Verification commands pass
  • Documentation is updated (both languages)
  • Change summary documents what was checked

❌ Cannot exit when:

  • Code changed but docs still describe old behavior
  • Backend changed but frontend still uses old contract
  • Frontend changed but backend compatibility not verified
  • One language docs updated but not the other

© ZeroDeng01, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/cross-layer-sync of ZeroDeng01/sublinkPro.

Open the folder on GitHubat commit 11479da

Compare with similar skills

Cross-Layer Change Sync Checklist next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cross-Layer Change Sync Checklist compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cross-Layer Change Sync Checklist this skillZeroDeng01/sublinkPro1.7k—~1.9kAutomated safety check: PassMIT
Google Style Code Docsjjmartres/opencode133—~1.9kAutomated safety check: PassMIT
Shift JSDoc Contractsshift-editor/shift343—~3.7kAutomated safety check: PassApache-2.0
Code Change Analysis Gatetelagod/code-abyss244—~532Automated safety check: NotesMIT
Clean Commentsertugrul-dmr/clean-code-skills195—~422Automated safety check: PassMIT
Readme Blueprint Generatorgithub/awesome-copilot40k2 repos~729Automated safety check: PassMIT

Similar skills

  • Google Style Code Docs

    jjmartres/opencode

    Applies Google Style documentation to Python docstrings, Go comments and Terraform descriptions, for writing new docs or reviewing existing ones.

    133 GitHub stars~1.9k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed

  • Shift JSDoc Contracts

    shift-editor/shift

    Guides writing JSDoc for Shift exported APIs as a stable caller contract, covering ownership, lifetime, side effects and nullability that TypeScript types cannot express.

    343 GitHub stars~3.7k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Code Change Analysis Gate

    telagod/code-abyss

    Checks what a code change touched, how far its impact reaches and whether design docs, tests and README files kept up, before commit or in review.

    244 GitHub stars~532 tokensUpdated 2 mo ago
    DevelopmentAuto-check: notes

  • Clean Comments

    ertugrul-dmr/clean-code-skills

    A skill your agent uses when writing, fixing, editing, or reviewing Python comments and docstrings.

    195 GitHub stars~422 tokensUpdated 5 mo ago
    DevelopmentAuto-check passed

  • Readme Blueprint Generator

    github/awesome-copilot

    Official

    Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation.

    40k GitHub starsUsed in 2 repos~729 tokens
    DevelopmentAuto-check passed

  • Diagram Design

    cathrynlavery/diagram-design

    Creates branded diagrams, from architecture, flowchart and sequence to charts and maps, as self-contained HTML with inline SVG, with import from draw.io, Mermaid and Excalidraw.

    44k GitHub starsUsed in 1 repo~7.5k tokens
    DevelopmentAuto-check passed

More from ZeroDeng01/sublinkPro

All 8 skills in this repo

  • Performance Check

    ZeroDeng01/sublinkPro

    Checklist for reviewing code changes that touch queries, APIs, rendering, caching or algorithms for performance, scalability and resource-usage problems.

    1.7k GitHub stars~1.8k tokensUpdated 2 days ago
    Auto-check passed

  • Security Review Checklist

    ZeroDeng01/sublinkPro

    Checklist-driven security review for changes to authentication, authorization, MFA, secrets, input validation and other security-critical code.

    1.7k GitHub stars~2.3k tokensUpdated 2 days ago
    Auto-check passed

  • SublinkPro Manager

    ZeroDeng01/sublinkPro

    Manages a SublinkPro proxy subscription server through natural language, adding nodes, building subscriptions and share links, and editing templates and tags.

    1.7k GitHub stars~7.2k tokensUpdated 2 days ago
    Auto-check passed

  • Post-Development Workflow

    ZeroDeng01/sublinkPro

    A required checklist for after code changes: validate each changed layer, check that docs and other layers stay in sync, and test before committing or opening a PR.

    1.7k GitHub stars~4.4k tokensUpdated 2 days ago
    Auto-check passed

  • Documentation Sync Check

    ZeroDeng01/sublinkPro

    Checklist for keeping README, feature, configuration, install and API docs in step with code changes in the same PR, including the Chinese copies.

    1.7k GitHub stars~2.6k tokensUpdated 2 days ago
    Auto-check passed

  • Pre-Commit Check Gate

    ZeroDeng01/sublinkPro

    Blocking checklist that runs formatting, lint and test commands for changed Go and frontend files before any git add, commit or pull request.

    1.7k GitHub stars~2.9k tokensUpdated 2 days ago
    Auto-check: notes

Categories

Questions about Cross-Layer Change Sync Checklist

What does Cross-Layer Change Sync Checklist do?

A checklist for keeping backend, frontend, documentation and skill API reference changes in step, so a change touching several layers lands in one commit or pull request. This skill is a checklist rather than an automated tool. Its core rule is that a change must be atomic across layers: when it touches the backend, frontend, docs or the project's skill API reference, every affected layer is updated in the same pull request or commit.

When should I use Cross-Layer Change Sync Checklist?

Cross-Layer Change Sync Checklist fits situations like: changing an API route or payload that the frontend also depends on; renaming a field or changing its validation across backend and frontend; updating user-facing text or error messages that appear in several places; checking that documentation still matches runtime behavior before opening a pull request.

How do I install Cross-Layer Change Sync Checklist in Claude Code?

Run `npx skills add ZeroDeng01/sublinkPro --skill cross-layer-sync -a claude-code`. Or copy the skill folder (.agents/skills/cross-layer-sync in ZeroDeng01/sublinkPro) into .claude/skills/cross-layer-sync in your project. Claude Code loads it when a task matches its description.

How do I install Cross-Layer Change Sync Checklist in Codex?

Run `npx skills add ZeroDeng01/sublinkPro --skill cross-layer-sync -a codex`. Or copy the skill folder (.agents/skills/cross-layer-sync in ZeroDeng01/sublinkPro) into .agents/skills/cross-layer-sync in your project. Codex loads it when a task matches its description.

Can I use Cross-Layer Change Sync Checklist in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ZeroDeng01/sublinkPro --skill cross-layer-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cross-layer-sync, .gemini/skills/cross-layer-sync, .github/skills/cross-layer-sync and .opencode/skills/cross-layer-sync in your project.

What does Cross-Layer Change Sync Checklist need to run?

Going by SKILL.md and its folder, Cross-Layer Change Sync Checklist needs the command-line tools its instructions call (yarn and go). Our summary lists: A project with separate backend, frontend and documentation layers.

Does Cross-Layer Change Sync Checklist access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cross-Layer Change Sync Checklist safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cross-Layer Change Sync Checklist use?

Cross-Layer Change Sync Checklist is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cross-Layer Change Sync Checklist use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cross-Layer Change Sync Checklist?

Skills that share tags, products or a category with Cross-Layer Change Sync Checklist: Google Style Code Docs (jjmartres/opencode, 133 stars), Shift JSDoc Contracts (shift-editor/shift, 343 stars), Code Change Analysis Gate (telagod/code-abyss, 244 stars) and Clean Comments (ertugrul-dmr/clean-code-skills, 195 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cross-Layer Change Sync Checklist?

ZeroDeng01 (a GitHub user) maintains it in ZeroDeng01/sublinkPro, which has 1,665 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 5, 2026.

Source: ZeroDeng01/sublinkPro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.