Skip to main content
affpapa.org
RU EN
rule official · GitHub

debian-linux — GitHub Copilot rule for Debian administration

This rule guides Copilot when it writes Debian administration advice, scripts, or docs. Use it for package workflows, service configuration, and security checks.

Install into GitHub Copilot · Manually: put the files in place All methods and platforms ↓ 
.github/instructions/debian-linux.instructions.md
Open on GitHub

What debian-linux does

The rule applies across project files and steers Copilot toward Debian Stable conventions. It asks for the release name when relevant, favors official Debian repositories, and separates interactive package commands (apt) from script commands (apt-get). Package inspection uses tools such as apt-cache policy, apt show, and dpkg -l.

For system configuration, it points to /etc and systemd drop-in files, with systemctl for service control and journalctl for logs. Security guidance covers AppArmor, limited sudo privileges, and verification after changes. Commands should be ready to copy, and destructive actions should include rollback steps. Firewall advice must identify whether it expects ufw or nftables.

What it helps with

  • choose apt commands for interactive package management
  • write Debian install scripts with apt-get
  • override a systemd service through a drop-in file
  • add verification and rollback steps for system changes

Example prompts for the agent

  • Prepare package update commands for Debian Stable and show how to verify the result.
  • Write a Debian package installation script using apt-get.
  • Suggest a safe systemd drop-in override and include checks plus rollback steps.

How to install debian-linux

Manually: put the files in place

.github/instructions/debian-linux.instructions.md

The applyTo field sets which files it applies to

Step by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use

Questions about debian-linux

How do I install debian-linux in GitHub Copilot?

Add the rule file at .github/instructions/debian-linux.instructions.md.

What does debian-linux do?

It guides Copilot’s Debian-focused advice, scripts, and documentation. The rule covers package management, service configuration, and security checks.

Which commands does the rule recommend for Debian services?

Use systemctl to manage services and journalctl to inspect logs. Store systemd overrides in drop-in files under /etc/systemd/system/<unit>.d/.

Source text

debian-linux.instructions.md · MIT 
---
description: 'Guidance for Debian-based Linux administration, apt workflows, and Debian policy conventions.'
applyTo: '**'
---

# Debian Linux Administration Guidelines

Use these instructions when writing guidance, scripts, or documentation intended for Debian-based systems.

## Platform Alignment

- Favor Debian Stable defaults and long-term support expectations.
- Call out the Debian release (`bookworm`, `bullseye`, etc.) when relevant.
- Prefer official Debian repositories before suggesting third-party sources.

## Package Management

- Use `apt` for interactive commands and `apt-get` for scripts.
- Inspect packages with `apt-cache policy`, `apt show`, and `dpkg -l`.
- Use `apt-mark` to track manual vs. auto-installed packages.
- Document any apt pinning in `/etc/apt/preferences.d/` and explain why.

## Configuration & Services

- Store configuration under `/etc` and avoid modifying `/usr` files directly.
- Use systemd drop-ins in `/etc/systemd/system/<unit>.d/` for overrides.
- Prefer `systemctl` and `journalctl` for service control and logs.
- Use `ufw` or `nftables` for firewall guidance; state which is expected.

## Security

- Account for AppArmor profiles and mention adjustments if needed.
- Recommend least-privilege `sudo` use and minimal package installs.
- Include verification commands after security changes.

## Deliverables

- Provide commands in copy-paste-ready blocks.
- Include validation steps after changes.
- Offer rollback steps for destructive actions.

© github · MIT · github/awesome-copilot

Similar IDE rules

All IDE rules for DevOps and infrastructure →

From the same set770

The whole set →
devops-core-principles Guides GitHub Copilot on CALMS principles, DORA metrics, and delivery automation across CI/CD pipelines and infrastructure as code. ★ 40,418repo stars devcontainers Twelve rules that make Copilot review devcontainer.json, Dev Container Features and Codespaces lifecycle settings, each with the exact fix and a source. ★ 40,418repo stars devbox-image-definition A GitHub Copilot rule that helps you write YAML image definition files for Microsoft Dev Box Team Customizations. Useful when your customizations rely on ~/winget, ~/gitclone and ~/powershell tasks. ★ 40,418repo stars declarative-agents-microsoft365 Development instructions for Microsoft 365 Copilot declarative agents using schema v1.5. Helps build TypeSpec models and valid manifests. ★ 40,418repo stars dataverse-python A GitHub Copilot rule that tells the agent how to set up the Dataverse Python SDK: install, environment variables and OAuth. ★ 40,418repo stars dataverse-python-testing-debugging Instructs GitHub Copilot on testing and debugging Python Dataverse SDK apps. Provides pytest fixture patterns, mock responses, and integration setups. ★ 40,418repo stars dataverse-python-sdk This rule gives GitHub Copilot Python SDK examples for Dataverse, from connecting to bulk updates and file uploads. Use it while building code that works with Dataverse. ★ 40,418repo stars dataverse-python-real-world-usecases A Copilot rule with Python templates for Dataverse migration and cleanup, so suggestions follow real integration patterns instead of generic advice. ★ 40,418repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor