gerrit
Interact with Storj Gerrit team code collaboration service, which we just called it gerrit, when the user ask to do it
What this skill does
# Storj Gerrit
Storj has a Gerrit service hosted on review.dev.storj.tools sub-domain. This document refers to it
as Gerrit.
The service allows read-only public access to the open source repositories. Write access requires
users to have an account.
This skill focus on users with write access.
Repositories are under `storj/` path. This repository URL is review.dev.storj.tools/c/storj/storj
This document use curly-brackets as variable values substitutions for URL, command, etc., patterns.
## Access configuration
Verify that the user has a Gerrit remote configured with SSH and the "commit-msg" hook is present.
`commit-msg` hook is in `.git/hooks/commit-msg`, must have executable permissions and its content
must have "From Gerrit Code Review".
Access is configured if user has both.
### "commit-msg" hook
If user doesn't have the hook download it executing
```
mkdir -p `git rev-parse --git-dir`/hooks/ \
&& curl -Lo `git rev-parse --git-dir`/hooks/commit-msg https://review.dev.storj.tools/tools/hooks/commit-msg \
&& chmod +x `git rev-parse --git-dir`/hooks/commit-msg
```
If it has it, but it doesn't contain "From Gerrit Code Review", tell them about it and to download
it manually and decide how to merge their logic.
### Configure remote
The use doesn't have a Gerrit remote configured.
Tell them that you need a remote to interact with Gerrit and they need to have an account; ask them
if they have one.
If they don't have it, tell them to ask to some Storj employee how to get one and to ask you again
to configure the access when they get it.
When they have an account, check if they have already a remote called `origin` and `gerrit`.
Ask them what's their username and what name they want for the Gerrit remote, suggesting `origin` if
it doesn't exist, otherwise `gerrit`, and if they have both list them to the user and don't suggest
any.
Add the new remote with
`git remote add {remote-name} "ssh://{username}@review.dev.storj.tools:29418/storj/storj"`
And download the hook as mentioned in the above "commit-msg hook" section.
## Post a review to a change
You can post review comments if you POST a json file to '/changes/{change-id}/revisions/{revision-id}/review'
`review.json` example:
```json
{
"tag": "jenkins",
"message": "Some nits need to be fixed.",
"labels": {
"Code-Review": -1
},
"comments": {
"gerrit-server/src/main/java/com/google/gerrit/server/project/RefControl.java": [
{
"line": 23,
"message": "[nit] trailing whitespace"
},
{
"line": 49,
"message": "[nit] s/conrtol/control"
},
{
"range": {
"start_line": 50,
"start_character": 0,
"end_line": 55,
"end_character": 20
},
"message": "Incorrect indentation"
}
]
}
}
```
You should use `./scripts/submit_review.sh` script to post reviews.
Example:
./scripts/submit_review.sh review.json $(git rev-parse HEAD)Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.