Code Review
Azure/sap-automation
Review pull requests in the SAP Deployment Automation Framework.
Expert manager for Gerrit multi-repository and multi-branch permission configurations.
Install Gerrit Permission Manager
$ npx skills add theneoai/awesome-skills --skill gerrit-permission-manager -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install theneoai/awesome-skills gerrit-permission-manager --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/theneoai/awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tool/security/gerrit-permission-manager .claude/skills/gerrit-permission-manager && rm -rf skills-srcUse ~/.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/
Install the "gerrit-permission-manager" agent skill from https://github.com/theneoai/awesome-skills/tree/main/skills/tool/security/gerrit-permission-manager into .claude/skills/gerrit-permission-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gerrit-permission-manager", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/theneoai/awesome-skills/tree/main/skills/tool/security/gerrit-permission-managerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add theneoai/awesome-skills --skill gerrit-permission-manager -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install theneoai/awesome-skills gerrit-permission-manager --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/theneoai/awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/tool/security/gerrit-permission-manager .agents/skills/gerrit-permission-manager && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gerrit-permission-manager" agent skill from https://github.com/theneoai/awesome-skills/tree/main/skills/tool/security/gerrit-permission-manager into .agents/skills/gerrit-permission-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gerrit-permission-manager", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add theneoai/awesome-skills --skill gerrit-permission-manager -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install theneoai/awesome-skills gerrit-permission-manager --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/theneoai/awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/tool/security/gerrit-permission-manager .cursor/skills/gerrit-permission-manager && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gerrit-permission-manager" agent skill from https://github.com/theneoai/awesome-skills/tree/main/skills/tool/security/gerrit-permission-manager into .cursor/skills/gerrit-permission-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gerrit-permission-manager", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/theneoai/awesome-skills.git --path skills/tool/security/gerrit-permission-manager--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add theneoai/awesome-skills --skill gerrit-permission-manager -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install theneoai/awesome-skills gerrit-permission-manager --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/theneoai/awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/tool/security/gerrit-permission-manager .gemini/skills/gerrit-permission-manager && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gerrit-permission-manager" agent skill from https://github.com/theneoai/awesome-skills/tree/main/skills/tool/security/gerrit-permission-manager into .gemini/skills/gerrit-permission-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gerrit-permission-manager", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install theneoai/awesome-skills gerrit-permission-managerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add theneoai/awesome-skills --skill gerrit-permission-manager -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/theneoai/awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/tool/security/gerrit-permission-manager .github/skills/gerrit-permission-manager && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gerrit-permission-manager" agent skill from https://github.com/theneoai/awesome-skills/tree/main/skills/tool/security/gerrit-permission-manager into .github/skills/gerrit-permission-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gerrit-permission-manager", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add theneoai/awesome-skills --skill gerrit-permission-manager -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install theneoai/awesome-skills gerrit-permission-manager --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/theneoai/awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/tool/security/gerrit-permission-manager .opencode/skills/gerrit-permission-manager && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gerrit-permission-manager" agent skill from https://github.com/theneoai/awesome-skills/tree/main/skills/tool/security/gerrit-permission-manager into .opencode/skills/gerrit-permission-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gerrit-permission-manager", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
gerrit-permission-manager- GitHub stars
- 185
- Token cost
- ~2.5k tokens
- SKILL.md length
- 913 words
- Files
- 29 (incl. scripts, references)
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Expert manager for Gerrit multi-repository and multi-branch permission configurations.
- Works in 4 steps: Request → Assessment → Coordination → …
- Working with Gerrit code review permissions
- SKILL.md covers § 1 · System Prompt, § 10 · Troubleshooting, § 11 · Edge Cases and § 12 · Related Skills, plus 6 more sections
- Access controls
What it does
Gerrit Permission Manager is an agent skill from theneoai/awesome-skills. Expert manager for Gerrit multi-repository and multi-branch permission configurations. Use when working with Gerrit code review permissions, access controls, repository groups, branch-level permissions, or manifest-based multi-repo management. Use when: gerrit, permissions, code-review, access-control, devops.
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 30 other files, including scripts and reference files (for example `references/cases.md`, `references/git-flow.md` and `references/glossary.md`).
It sits in Development, covering Authorization and RBAC and Code review. The repository describes itself as: 🌟1000+ Expert AI Skills | CEO, Doctor, Engineer, Scientist & more | Transform AI into any professional | Powered by https://theneoai.github.io/skill-writer/. The licence is MIT.
When your agent uses it
- Working with Gerrit code review permissions
- Access controls
- Repository groups
- Branch-level permissions
Example prompts
- “/gerrit-permission-manager”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 61fe4f2. 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
Ships 1 file in scripts/, which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
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
Gerrit Permission Manager loads about 2.5k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 84 tokens; SKILL.md has 913 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
The full file from theneoai/awesome-skills at commit 61fe4f2, republished under its MIT licence (© theneoai). 913 words, ~2,489 tokens.
Download SKILL.mdSave it as
.claude/skills/gerrit-permission-manager/SKILL.md (or your agent's skills folder). This skill also uses 28 other files; get the full folder from GitHub.- name
- gerrit-permission-manager
- description
- Expert manager for Gerrit multi-repository and multi-branch permission configurations. Use when working with Gerrit code review permissions, access controls, repository groups, branch-level permissions, or manifest-based multi-repo management. Use when: gerrit, permissions, code-review, access-control, devops.
- kind
- tool
- version
- 1.0.0
- tags
- - domain: special - subtype: gerrit-permission-manager - level: expert
- license
- MIT
- metadata
- author: theNeoAI <lucas_hsueh@hotmail.com>
Gerrit Permission Manager
§ 1 · System Prompt
1.1 Role Definition
Identity: You are a senior gerrit permission manager with 15+ years at top-tier technology companies (FAANG, BAT, top-tier startups). You've led mission-critical projects serving millions of users and architected systems handling billions of daily transactions.
Core Expertise:
- Deep mastery of gerrit architecture and implementation patterns
- Proven track record delivering high-scale, high-reliability systems (99.99%+ uptime)
- Expert in cross-functional collaboration with design, product, and business teams
- Pioneer in adopting and adapting cutting-edge technologies for production use
1.2 Decision Framework
First Principles:
- Evidence-Based — Decisions backed by data, research, or proven methodology
- Risk-Aware — Proactively identify and mitigate risks
- Outcome-Focused — Every recommendation tied to measurable results
- Continuous Learning — Incorporate latest research and best practices
Domain-Specific Criteria:
| Priority | Factor | Key Considerations |
|---|---|---|
| 1 | System Reliability | 99.99% uptime |
| 2 | Quality | Exceed industry standards |
| 3 | Efficiency | Optimize resource utilization |
| 4 | Innovation | Adopt proven innovations |
1.3 Thinking Patterns
Analytical: Data-driven decomposition, root cause analysis, statistical validation Creative: Cross-domain pattern matching, first-principles thinking, rapid prototyping Pragmatic: Constraint optimization, stakeholder alignment, delivery focus
§ 10 · Troubleshooting
→ Full troubleshooting guide: references/08-troubleshooting.md
| Problem | Root Cause | Quick Fix | Verification |
|---|---|---|---|
| Permission denied on push | Group membership missing | Check: gerrit ls-groups --member user@domain | User can push test commit |
| Cannot submit change | Missing submit permission or labels | Verify submit permission + required label scores | Submit button enabled |
| Group not found | UUID mismatch across environments | Check UUID: gerrit ls-groups -v group-name | Group resolves correctly |
| Manifest sync fails | Manifest repo read access denied | Grant read access on manifest repo | repo sync succeeds |
| REST API 403 | HTTP password or SSH key issue | Generate HTTP password; verify SSH key | API returns 200 |
| Drift detected after template apply | Manual overrides present | Re-apply template with --force flag | Drift check passes |
| Anonymous access flagged | Registered Users group too broad | Restrict to specific groups | Unauthenticated access denied |
| Inheritance not working | Child project override flag set | Check parent project settings | Inheritance chain intact |
| User removed but still has access | Gerrit auth cache | Flush caches: gerrit flush-caches --cache accounts | Access denied as expected |
| Bulk update partial failure | Manifest syntax error | Dry run first: --dry-run --verbose | All repos updated |
§ 11 · Edge Cases
| Situation | Handling | Validation |
|---|---|---|
| Repository inheritance not working | Check child project override flags | Verify parent permissions propagate |
| User removed but still has access | Gerrit caches auth; run gerrit flush-caches --cache accounts | Confirm access revoked |
| Bulk update fails on partial manifest | Dry run first: --dry-run --verbose | All-or-nothing atomic update |
| Code owner approval required | Ensure OWNERS file exists with approvers | Submit blocked without owner approval |
| PCI-DSS compliance required | Use pci-dss compliance flag in audit | Pass all PCI-DSS checks |
| Graduated permissions | Use group promotion workflow over time | Track permission changes |
| Circular group nesting | Detect and break cycles | Group hierarchy is DAG |
| Empty group grants | Remove or populate empty groups | No empty groups with permissions |
| Orphaned repository permissions | Clean up when repo deleted | No stale permission entries |
| Cross-environment group sync | Use UUID mapping file | Groups match across dev/staging/prod |
§ 12 · Related Skills
| Skill | Relationship | When to Use Together |
|---|---|---|
| devops-engineer | DevOps integration with CI/CD pipelines | Configuring CI bot permissions |
| security-auditor | Security compliance and audit reporting | Deep security analysis required |
| cloud-architect | Multi-cloud Gerrit deployment | Designing distributed Gerrit setups |
| git-workflow-expert | Git branching strategy design | Implementing git-flow permissions |
Show full SKILL.md (381 more words)Show less
§ 13 · Change Log
| Version | Date | Changes | Author |
|---|---|---|---|
| 1.0.0 | 2026-01-15 | Initial release | neo.ai |
| 2.0.0 | 2026-02-01 | Added templates and Git Flow support | neo.ai |
| 3.0.0 | 2026-03-16 | Full reference files added; comprehensive guide | neo.ai |
| 3.1.0 | 2026-03-21 | 16-section standard format compliance; enhanced risk matrix; detailed workflow phases; expanded scenario examples | neo.ai |
§ 14 · Contributing
Original Author: Neo.ai (@neoai) Source Repository: https://github.com/neoai/awesome-skills License: MIT License — Copyright (c) 2026 Neo.ai
Contribution Guidelines:
- Submit issues and PRs to the source repository
- Follow the existing documentation style
- Include test cases for new templates
- Update change log with each contribution
Reference documentation by the awesome-skills community.
§ 15 · Final Notes
Best Practices Summary
Gerrit permission management works best when:
- Group structure is defined before assigning permissions — Groups are the foundation
- Templates are used for consistency across repositories — Don't reinvent per repo
- Inheritance from parent projects is leveraged — Reduces duplication
- Least privilege is enforced — Minimize attack surface
- Security audits run regularly — Catch drift early
- Drift detection compares against baseline templates — Maintain compliance
Quick Reference Card
┌─────────────────────────────────────────────────────────────┐
│ GERRIT PERMISSION MANAGER QUICK REF │
├─────────────────────────────────────────────────────────────┤
│ 1. Always start with groups, not individuals │
│ 2. Use templates: standard | restricted | protected │
│ 3. Test in non-prod before production │
│ 4. Backup before changes: export refs/meta/config │
│ 5. Run audit after changes: ./scripts/audit-permissions.sh │
│ 6. Enable drift detection for ongoing compliance │
└─────────────────────────────────────────────────────────────┘Full reference documentation available in the references/ directory.
§ 16 · Install Guide
For OpenCode (recommended)
/skill install gerrit-permission-managerManual Install
- Copy the YAML frontmatter and §1 System Prompt section
- Paste into your agent's skill configuration
- Reference files in
references/are optional—SKILL.md works standalone
Platform-Specific Instructions
| Platform | Location | Notes |
|---|---|---|
| OpenCode | ~/.opencode/skills/gerrit-permission-manager.md | Auto-loads on startup |
| Claude Code | ~/.claude/CLAUDE.md | Append to existing file |
| Cursor | ~/.cursor/rules/gerrit-permission-manager.mdc | MDC format required |
| Kimi | .kimi-rules | Project-local or global |
Verification
After installing, try:
"Help me set up branch protection for our main branch"Expected response includes:
- Template selection guidance
- Group verification steps
- Branch pattern recommendations
- Security score prediction
License: MIT License — Copyright (c) 2026 Neo.ai
References
Detailed content:
- ## § 2 · What This Skill Does
- ## § 3 · Risk Documentation
- ## § 4 · Core Philosophy
- ## § 6 · Professional Toolkit
- ## § 7 · Standards & Reference
- ## § 8 · Workflow
- ## § 9 · Scenario Examples
- ## § 20 · Case Studies
Workflow
Phase 1: Request
- Receive and document request
- Clarify requirements and constraints
- Assess urgency and priority
Done: Request documented, requirements clarified Fail: Unclear request, missing information
Phase 2: Assessment
- Evaluate current state and gaps
- Identify resources needed
- Assess risks and alternatives
Done: Assessment complete, solution options identified Fail: Incomplete assessment, missed risks
Phase 3: Coordination
- Coordinate with stakeholders
- Allocate resources
- Execute plan
Done: Coordination complete, plan executed Fail: Resource conflicts, stakeholder issues
Phase 4: Resolution & Confirmation
- Verify resolution meets requirements
- Obtain stakeholder sign-off
- Document lessons learned
Done: Issue resolved, stakeholder approved Fail: Recurring issues, no sign-off
© theneoai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 28 other files (scripts, references) in skills/tool/security/gerrit-permission-manager of theneoai/awesome-skills.
- SKILL.md
- references/cases.md
- references/git-flow.md
- references/glossary.md
- references/overview.md
- references/permission-templates.md
- references/philosophy.md
- references/risk-documentation.md
- references/scenarios.md
- references/standards.md
- references/templates/git-flow.json
- references/templates/multi-team.json
- references/templates/protected-branches.json
- references/templates/restricted.json
- references/templates/standard.json
- references/toolkit.md
- references/troubleshooting.md
- references/workflow.md
- scripts
- … and 10 more
Open the folder on GitHubat commit 61fe4f2
Compare with similar skills
Gerrit Permission Manager 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Gerrit Permission Manager this skilltheneoai/awesome-skills | 185 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Code ReviewAzure/sap-automation | 146 | — | ~7k | Automated safety check: Pass | MIT | |
| Code Review SecurityOWASP/secure-agent-playbook | 188 | — | ~549 | Automated safety check: Pass | CC-BY-4.0 | |
| SQL Code Reviewtotvs/engpro-advpl-tlpp-skills | 143 | — | ~3.5k | Automated safety check: Pass | MIT | |
| SQL Code Reviewgithub/awesome-copilot | 40k | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Phx Planoliver-kriska/claude-elixir-phoenix | 565 | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
- Official
Code Review Security
OWASP/secure-agent-playbook
Security-focused code review mapped to OWASP Top 10 and ASVS.
SQL Code Review
totvs/engpro-advpl-tlpp-skills
Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across SQL databases (PostgreSQL, SQL Server, Oracle).
- Official
SQL Code Review
github/awesome-copilot
Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle).
Phx Plan
oliver-kriska/claude-elixir-phoenix
Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban).
Plan
oliver-kriska/claude-elixir-phoenix
Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban).
More from theneoai/awesome-skills
All 11 skills in this repoAbaqus Expert
theneoai/awesome-skills
Invoke when: User needs help with Abaqus FEA, nonlinear analysis, contact mechanics, or material modeling.
Abaqus Lhs Batch Dataset
theneoai/awesome-skills
Generate an Abaqus FEA training dataset for surrogate / ML models.
Abaqus Odb To Grid CSV
theneoai/awesome-skills
Convert per-case Abaqus FEA outputs into ML-ready (X, Y) wide-table CSVs.
Abaqus Surrogate Fea Validation
theneoai/awesome-skills
Closed-loop inverse-design validation. An agent skill from theneoai/awesome-skills.
Academic Advisor
theneoai/awesome-skills
Expert Academic Advisor specializing in academic planning, degree requirements, student success coaching, and career pathway integration.
Academic Director
theneoai/awesome-skills
Expert Academic Director with 20+ years experience in K-12 or higher education administration, curriculum planning, teacher supervision, and academic standards.
Related
Categories
Questions about Gerrit Permission Manager
What does Gerrit Permission Manager do?
Expert manager for Gerrit multi-repository and multi-branch permission configurations. Gerrit Permission Manager is an agent skill from theneoai/awesome-skills. Expert manager for Gerrit multi-repository and multi-branch permission configurations.
When should I use Gerrit Permission Manager?
Gerrit Permission Manager fits situations like: working with Gerrit code review permissions; access controls; repository groups; branch-level permissions.
How do I install Gerrit Permission Manager in Claude Code?
Run `npx skills add theneoai/awesome-skills --skill gerrit-permission-manager -a claude-code`. Or copy the skill folder (skills/tool/security/gerrit-permission-manager in theneoai/awesome-skills) into .claude/skills/gerrit-permission-manager in your project. Claude Code loads it when a task matches its description.
How do I install Gerrit Permission Manager in Codex?
Run `npx skills add theneoai/awesome-skills --skill gerrit-permission-manager -a codex`. Or copy the skill folder (skills/tool/security/gerrit-permission-manager in theneoai/awesome-skills) into .agents/skills/gerrit-permission-manager in your project. Codex loads it when a task matches its description.
Can I use Gerrit Permission Manager 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 theneoai/awesome-skills --skill gerrit-permission-manager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gerrit-permission-manager, .gemini/skills/gerrit-permission-manager, .github/skills/gerrit-permission-manager and .opencode/skills/gerrit-permission-manager in your project.
What does Gerrit Permission Manager need to run?
SKILL.md names no scripts, command-line tools or credentials: Gerrit Permission Manager is instructions for the agent only.
Does Gerrit Permission Manager access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Gerrit Permission Manager 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Gerrit Permission Manager use?
Gerrit Permission Manager is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Gerrit Permission Manager use?
About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 15k tokens, read only when the agent opens those files.
What are the alternatives to Gerrit Permission Manager?
Skills that share tags, products or a category with Gerrit Permission Manager: Code Review (Azure/sap-automation, 146 stars), Code Review Security (OWASP/secure-agent-playbook, 188 stars), SQL Code Review (totvs/engpro-advpl-tlpp-skills, 143 stars) and SQL Code Review (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Gerrit Permission Manager?
theneoai (a GitHub user) maintains it in theneoai/awesome-skills, which has 185 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on May 15, 2026.
Source: theneoai/awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.