CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

mdelapenya/coding-skills

Coding-agent skills for pull-request work and orchestration: an adversarial multi-pass PR reviewer, PR description and title writing, answering review comments, CI failure triage and PR nursing, a DAG orchestrator that delegates to cheaper subagents, and file-channel coordination between agents. Supports GitHub and GitLab.

1.88x
Quality

95%

Does it follow best practices?

Impact

98%

1.88x

Average score across 10 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

gitlab.mdskills/pr-lawyer/references/

GitLab

Platform-specific commands for responding to merge request review comments on GitLab.

Detect

The repository uses GitLab if git remote -v shows gitlab.com URLs.

Fetch unresolved discussion threads

glab api projects/<project-id>/merge_requests/<iid>/discussions \
  --jq '[.[] | select(.resolved == false) | {id, notes: [.notes[] | {id, body, author: .author.username, resolvable, resolved}]}]'

To get note permalinks, construct them from the MR web URL:

https://gitlab.com/<namespace>/<repo>/-/merge_requests/<iid>#note_<note-id>

Use these links when replying to reference the original comment.

Where <project-id> is the URL-encoded namespace/repo (e.g. org%2Frepo).

Fetch MR diff for context

glab mr diff <iid>

Reply to a discussion thread

glab api projects/<project-id>/merge_requests/<iid>/discussions/<discussion-id>/notes \
  --method POST \
  --field body="<reply>"

Resolve a discussion thread

glab api projects/<project-id>/merge_requests/<iid>/discussions/<discussion-id> \
  --method PUT \
  --field resolved=true

Resolve a thread after fixing the related code to signal the issue is addressed.

LICENSE

README.md

tile.json