qwen-code-permission

Modify Qwen Code permission rules in settings.json via Python script.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/CNife/skills --skill qwen-code-permission
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qwen-code-permission
Source: https://github.com/CNife/skills/tree/main/.archive/qwen-code-permission
Command: npx skills add https://github.com/CNife/skills --skill qwen-code-permission

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes the friction of editing Qwen Code permission rules by hand, helping you quickly control when commands are allowed, prompted for confirmation, or denied.

Core Features & Use Cases

  • Permission Rule Management: Add or update allow, ask, and deny entries in settings.json with consistent rule handling.
  • Tool and Pattern Coverage: Work with Qwen Code tool aliases, wildcard command patterns, and path-based rules for precise control.
  • Use Case: Use it when you want to auto-approve a safe command, require confirmation for risky Git actions, or block destructive shell operations.

Quick Start

Ask the Skill to add the permission rule Bash(git *) to the allow list in your Qwen Code settings and apply the change.

Frequently Asked Questions about qwen-code-permission

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

FAQPage Schema
How do I configure allow and deny lists in Qwen Code settings.json?

You can configure Qwen Code permissions by adding allow, ask, and deny entries to settings.json. This automates updating Bash, Read, Edit, WebFetch, and Agent tool patterns, letting you auto-approve safe commands or block destructive shell operations.

What's the best way to auto-approve safe Git commands in Qwen Code?

To auto-approve safe Git commands in Qwen Code, add the wildcard pattern Bash(git *) to the allow list in settings.json. This applies deterministic updates through a Python script executed with uv, removing the friction of manual permission rule editing.

Can I require confirmation before running risky shell operations in Qwen Code?

Yes, you can require confirmation for risky shell operations by adding them to the ask list in settings.json. This manages Qwen Code permissions by prompting for confirmation before executing destructive commands, ensuring safer troubleshooting and configuration.

Does Qwen Code permission management support path-based rules and tool aliases?

Qwen Code permission management supports tool aliases, wildcard command patterns, and path-based rules. It modifies allow, ask, and deny entries for Bash, Read, Edit, WebFetch, Agent, and Skill tools within settings.json.

Do I need uv to run Qwen Code permission scripts?

Yes, you need uv to execute the Python script that applies deterministic updates to Qwen Code permission rules. You also need an existing settings.json file to add or update allow, ask, and deny entries for tool patterns.