manage-bans Skill
Create and manage banned AST patterns that prevent specific code constructs. Use when the user wants to ban a code pattern, add a tree-sitter lint rule, or prevent specific syntax from appearing in edits. Published by microsoft in vscode-team-kit.
What is manage-bans Skill?
Create and manage banned AST patterns that prevent specific code constructs. Use when the user wants to ban a code pattern, add a tree-sitter lint rule, or prevent specific syntax from appearing in edits. Published by microsoft in vscode-team-kit. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Documentation
- Security review use cases
- Documentation use cases
Technical details
- Install or run with Copy skill directory
When to use manage-bans Skill
- Use it for security review.
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-team-kit
- Skill file: ban-ast/skills/manage-bans/SKILL.md
What it does
Create and manage banned AST patterns that prevent specific code constructs. Use when the user wants to ban a code pattern, add a tree-sitter lint rule, or prevent specific syntax from appearing in edits.
Skill instructions
Managing Banned AST Patterns Ban rules are discovered from two sources, both checked by the preToolUse hook: 1. $HOME/.BANNEDAST.md — global rules that apply to all edits, regardless of project. 2. BANNEDAST.md files in any parent directory of the edited file — can contain multiple rules, scoped to that subtree. Source 1: Global Ban File ($HOME/.BANNEDAST.md) Place a BANNEDAST.md in your home directory to define rules that apply globally to every edit. It uses the same multi-rule format as directory-scoped files: markdown --- name: no-eval message: "Do not use eval(). It poses a security risk and should be replaced with safer alternatives." --- (callexpression function: (identifier) @fn (eq? @fn "eval")) Creating a Global Ban 1. Open or create ~/.BANNEDAST.md. 2. Add a rule block with --- frontmatter containing name and message, followed by --- and the Tree Sitter query. 3. Multiple rules can be stacked in the same file, each separated by a new frontmatter block. 4. Validate the rule —
Explore related resources
Frequently asked questions
What is manage-bans?
manage-bans is a open-source AI agent skill with Copy skill directory. Create and manage banned AST patterns that prevent specific code constructs. Use when the user wants to ban a code pattern, add a tree-sitter lint rule, or prevent specific syntax from appearing in edits.
Who is manage-bans best for?
manage-bans is best for reusing agent instructions, scripts, and references, security review workflows, documentation workflows.
How do I install manage-bans?
Install or run manage-bans using Copy skill directory. Check manage-bans for the latest setup command.
Is manage-bans actively maintained?
manage-bans may need a closer maintenance check before production use.
Auto-fetched from GitHub.
